Prioritized messaging and resource selection in vehicle-to-vehicle (v2v) sidelink communication

ABSTRACT

Embodiments of a Generation Node-B (gNB), User Equipment (UE) and methods for communication are generally described herein. The gNB may allocate a resource pool of physical resource blocks (PRBs) and sub-frames for vehicle-to-vehicle (V2V) sidelink transmissions. The gNB may receive, from a UE, an uplink control message that indicates that the UE requests a V2V sidelink transmission of a prioritized message. The gNB may select, for the V2V sidelink transmission of the prioritized message, one or more PRBs and one or more sub-frames. The gNB may transmit, to the UE and to other UEs, a downlink control message that indicates: the selected PRBs, the selected sub-frames, and that the other UEs are to mute sidelink transmissions in the selected PRBs in the selected sub-frames to enable the V2V sidelink transmission of the prioritized message.

PRIORITY CLAIM

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 62/475,471, filed Mar. 23, 2017, and to U.S. Provisional PatentApplication Ser. No. 62/587,382, filed Nov. 16, 2017, both of which areincorporated herein by reference in their entirety.

TECHNICAL FIELD

Embodiments pertain to wireless communications. Some embodiments relateto wireless networks including 3GPP (Third Generation PartnershipProject) networks, 3GPP LTE (Long Term Evolution) networks, and 3GPPLTE-A (LTE Advanced) networks. Some embodiments relate to FifthGeneration (5G) networks. Some embodiments relate to New Radio (NR)networks. Some embodiments relate to sidelink communication. Someembodiments relate to vehicle-to-vehicle (V2V) communication. Someembodiments relate to transmission of prioritized signals, emergencysignals and/or signals for which ultra high reliability of reception istargeted, including transmission of such signals in V2V sidelinkarrangements.

BACKGROUND

Mobile devices may exchange data in accordance with sidelinkradio-protocols for communication, which may be challenging in someaspects. For instance, high reliability of reception may be challenging,especially in systems with distributed access to resources. In somecases, such as when mobile devices are out of network coverage, themobile devices may perform sidelink communication autonomously withlimited or no assistance from a base station. In other cases, a basestation may provide assistance to the mobile devices for various tasks,such as allocation of resources, signaling of control messages and/orothers. Various use cases for sidelink communication are possible. In anexample scenario, sidelink communication in accordance with a lowlatency and high reliability may be used. In another example scenario,high priority messages may be exchanged between mobile devices usingsidelink communication. There is a general need for methods and systemsto enable sidelink communication and to target high reliability ofreception in these and other scenarios.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a functional diagram of an example network in accordance withsome embodiments;

FIG. 1B is a functional diagram of another example network in accordancewith some embodiments;

FIG. 2 illustrates a block diagram of an example machine in accordancewith some embodiments;

FIG. 3 illustrates a user device in accordance with some aspects:

FIG. 4 illustrates a base station in accordance with some aspects;

FIG. 5 illustrates an exemplary communication circuitry according tosome aspects;

FIG. 6 illustrates an example of a radio frame structure in accordancewith some embodiments:

FIG. 7A and FIG. 7B illustrate example frequency resources in accordancewith some embodiments;

FIG. 8 illustrates the operation of a method of communication inaccordance with some embodiments;

FIG. 9 illustrates the operation of another method of communication inaccordance with some embodiments;

FIG. 10 illustrates example signaling that may be exchanged inaccordance with some embodiments;

FIG. 11A, FIG. 11B, and FIG. 11C illustrate an example of a mediumaccess control (MAC) control element (CE) that may be exchanged inaccordance with some embodiments;

FIG. 12 illustrates an example of a system information block (SIB)element that may be exchanged in accordance with some embodiments; and

FIG. 13 illustrates example signaling that may be exchanged inaccordance with some embodiments.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

FIG. 1A is a functional diagram of an example network in accordance withsome embodiments. FIG. 1B is a functional diagram of another examplenetwork in accordance with some embodiments. In references herein, “FIG.1” may include FIG. 1A and FIG. 1B. In some embodiments, the network 100may be a Third Generation Partnership Project (3GPP) network. In someembodiments, the network 150 may be a 3GPP network. In a non-limitingexample, the network 150 may be a new radio (NR) network. It should benoted that embodiments are not limited to usage of 3GPP networks,however, as other networks may be used in some embodiments. As anexample, a Fifth Generation (5G) network may be used in some cases. Asanother example, a New Radio (NR) network may be used in some cases. Asanother example, an LTE (E-UTRAN) network may be used in some cases. Asanother example, a wireless local area network (WLAN) may be used insome cases. Embodiments are not limited to these example networks,however, as other networks may be used in some embodiments. In someembodiments, a network may include one or more components shown in FIG.1A. Some embodiments may not necessarily include all components shown inFIG. 1A. and some embodiments may include additional components notshown in FIG. 1A. In some embodiments, a network may include one or morecomponents shown in FIG. 1B. Some embodiments may not necessarilyinclude all components shown in FIG. 1B, and some embodiments mayinclude additional components not shown in FIG. 1B. In some embodiments,a network may include one or more components shown in FIG. 1A and one ormore components shown in FIG. 1B. In some embodiments, a network mayinclude one or more components shown in FIG. 1A, one or more componentsshown in FIG. 1B and one or more additional components.

The network 100 may comprise a radio access network (RAN) 101 and thecore network 120 (e.g., shown as an evolved packet core (EPC)) coupledtogether through an S1 interface 115. For convenience and brevity sake,only a portion of the core network 120, as well as the RAN 101, isshown. In a non-limiting example, the RAN 101 may be an evolveduniversal terrestrial radio access network (E-UTRAN). In anothernon-limiting example, the RAN 101 may include one or more components ofa New Radio (NR) network. In another non-limiting example, the RAN 101may include one or more components of an E-UTRAN and one or morecomponents of another network (including but not limited to an NRnetwork).

The core network 120 may include a mobility management entity (MME) 122,a serving gateway (serving GW) 124, and packet data network gateway (PDNGW) 126. In some embodiments, the network 100 may include (and/orsupport) one or more Evolved Node-B's (eNBs) 104 (which may operate asbase stations) for communicating with User Equipment (UE) 102. The eNBs104 may include macro eNBs and low power (LP) eNBs, in some embodiments.

In some embodiments, the network 100 may include (and/or support) one ormore Generation Node-B's (gNBs) 105. In some embodiments, one or moreeNBs 104 may be configured to operate as gNBs 105. Embodiments are notlimited to the number of eNBs 104 shown in FIG. 1A or to the number ofgNBs 105 shown in FIG. 1A. In some embodiments, the network 100 may notnecessarily include eNBs 104. Embodiments are also not limited to theconnectivity of components shown in FIG. 1A.

It should be noted that references herein to an eNB 104 or to a gNB 105are not limiting. In some embodiments, one or more operations, methodsand/or techniques (such as those described herein) may be practiced by abase station component (and/or other component), including but notlimited to a gNB 105, an eNB 104, a serving cell, a transmit receivepoint (TRP) and/or other. In some embodiments, the base stationcomponent may be configured to operate in accordance with a New Radio(NR) protocol and/or NR standard, although the scope of embodiments isnot limited in this respect. In some embodiments, the base stationcomponent may be configured to operate in accordance with a FifthGeneration (5G) protocol and/or 5G standard, although the scope ofembodiments is not limited in this respect.

In some embodiments, one or more of the UEs 102. eNBs 104 and/or gNBs105 may be configured to operate in accordance with an NR protocoland/or NR techniques. References to a UE 102, eNB 104 and/or gNB 105 aspart of descriptions herein are not limiting. For instance, descriptionsof one or more operations, techniques and/or methods practiced by a gNB105 are not limiting. In some embodiments, one or more of thoseoperations, techniques and/or methods may be practiced by an eNB 104and/or other base station component.

In some embodiments, the UE 102 may transmit signals (data, controland/or other) to the gNB 105, and may receive signals (data, controland/or other) from the gNB 105. In some embodiments, the UE 102 maytransmit signals (data, control and/or other) to the eNB 104, and mayreceive signals (data, control and/or other) from the eNB 104. Theseembodiments will be described in more detail below.

The MME 122 is similar in function to the control plane of legacyServing GPRS Support Nodes (SGSN). The MME 122 manages mobility aspectsin access such as gateway selection and tracking area list management.The serving GW 124 terminates the interface toward the RAN 101, androutes data packets between the RAN 101 and the core network 120. Inaddition, it may be a local mobility anchor point for inter-gNBhandovers and/or inter-eNB handovers and also may provide an anchor forinter-3GPP mobility. Other responsibilities may include lawfulintercept, charging, and some policy enforcement. The serving GW 124 andthe MME 122 may be implemented in one physical node or separate physicalnodes. The PDN GW 126 terminates an SGi interface toward the packet datanetwork (PDN). The PDN GW 126 routes data packets between the EPC 120and the external PDN, and may be a key node for policy enforcement andcharging data collection. It may also provide an anchor point formobility with non-LTE accesses. The external PDN can be any kind of IPnetwork, as well as an IP Multimedia Subsystem (IMS) domain. The PDN GW126 and the serving GW 124 may be implemented in one physical node orseparated physical nodes.

In some embodiments, the eNBs 104 and/or gNBs 105 (macro and micro)terminate the air interface protocol and may be the first point ofcontact for a UE 102. In some embodiments, an eNB 104 and/or gNB 105 mayfulfill various logical functions for the network 100, including but notlimited to RNC (radio network controller functions) such as radio bearermanagement, uplink and downlink dynamic radio resource management anddata packet scheduling, and mobility management.

In some embodiments, UEs 102 may be configured to communicate OrthogonalFrequency Division Multiplexing (OFDM) communication signals with an eNB104 and/or gNB 105 over a multicarrier communication channel inaccordance with an Orthogonal Frequency Division Multiple Access (OFDMA)communication technique. In some embodiments, eNBs 104 and/or gNBs 105may be configured to communicate OFDM communication signals with a UE102 over a multicarrier communication channel in accordance with anOFDMA communication technique. The OFDM signals may comprise a pluralityof orthogonal subcarriers.

The S1 interface 115 is the interface that separates the RAN 101 and theEPC 120. It may be split into two parts: the S1-U, which carries trafficdata between the eNBs 104 and the serving GW 124, and the S1-MME, whichis a signaling interface between the eNBs 104 and the MME 122. The X2interface is the interface between eNBs 104. The X2 interface comprisestwo parts, the X2-C and X2-U. The X2-C is the control plane interfacebetween the eNBs 104, while the X2-U is the user plane interface betweenthe eNBs 104.

In some embodiments, similar functionality and/or connectivity describedfor the eNB 104 may be used for the gNB 105, although the scope ofembodiments is not limited in this respect. In a non-limiting example,the S1 interface 115 (and/or similar interface) may be split into twoparts: the S1-U, which carries traffic data between the gNBs 105 and theserving GW 124, and the S1-MME, which is a signaling interface betweenthe gNBs 104 and the MME 122. The X2 interface (and/or similarinterface) may enable communication between eNBs 104, communicationbetween gNBs 105 and/or communication between an eNB 104 and a gNB 105.

With cellular networks, LP cells are typically used to extend coverageto indoor areas where outdoor signals do not reach well, or to addnetwork capacity in areas with very dense phone usage, such as trainstations. As used herein, the term low power (LP) eNB refers to anysuitable relatively low power eNB for implementing a narrower cell(narrower than a macro cell) such as a femtocell, a picocell, or a microcell. Femtocell eNBs are typically provided by a mobile network operatorto its residential or enterprise customers. A femtocell is typically thesize of a residential gateway or smaller and generally connects to theuser's broadband line. Once plugged in, the femtocell connects to themobile operator's mobile network and provides extra coverage in a rangeof typically 30 to 50 meters for residential femtocells. Thus, a LP eNBmight be a femtocell eNB since it is coupled through the PDN GW 126.Similarly, a picocell is a wireless communication system typicallycovering a small area, such as in-building (offices, shopping malls,train stations, etc.), or more recently in-aircraft. A picocell eNB cangenerally connect through the X2 link to another eNB such as a macro eNBthrough its base station controller (BSC) functionality. Thus, LP eNBmay be implemented with a picocell eNB since it is coupled to a macroeNB via an X2 interface. Picocell eNBs or other LP eNBs may incorporatesome or all functionality of a macro eNB. In some cases, this may bereferred to as an access point base station or enterprise femtocell. Insome embodiments, various types of gNBs 105 may be used, including butnot limited to one or more of the eNB types described above.

In some embodiments, the network 150 may include one or more componentsconfigured to operate in accordance with one or more 3GPP standards,including but not limited to an NR standard. The network 150 shown inFIG. 1B may include a next generation RAN (NG-RAN) 155, which mayinclude one or more gNBs 105. In some embodiments, the network 150 mayinclude the E-UTRAN 160, which may include one or more eNBs. The E-UTRAN160 may be similar to the RAN 101 described herein, although the scopeof embodiments is not limited in this respect.

In some embodiments, the network 150 may include the MME 165. The MME165 may be similar to the MME 122 described herein, although the scopeof embodiments is not limited in this respect. The MME 165 may performone or more operations or functionality similar to those describedherein regarding the MME 122, although the scope of embodiments is notlimited in this respect.

In some embodiments, the network 150 may include the SGW 170. The SGW170 may be similar to the SGW 124 described herein, although the scopeof embodiments is not limited in this respect. The SGW 170 may performone or more operations or functionality similar to those describedherein regarding the SGW 124, although the scope of embodiments is notlimited in this respect.

In some embodiments, the network 150 may include component(s) and/ormodule(s) for functionality for a user plane function (UPF) and userplane functionality for PGW (PGW-U), as indicated by 175, someembodiments, the network 150 may include component(s) and/or module(s)for functionality for a session management function (SMF) and controlplane functionality for PGW (PGW-C), as indicated by 180. In someembodiments, the component(s) and/or module(s) indicated by 175 and/or180 may be similar to the PGW 126 described herein, although the scopeof embodiments is not limited in this respect. The component(s) and/ormodule(s) indicated by 175 and/or 180 may perform one or more operationsor functionality similar to those described herein regarding the PGW126, although the scope of embodiments is not limited in this respect.One or both of the components 170, 172 may perform at least a portion ofthe functionality described herein for the PGW 126, although the scopeof embodiments is not limited in this respect.

Embodiments are not limited to the number or type of components shown inFIG. 1B. Embodiments are also not limited to the connectivity ofcomponents shown in FIG. 1B.

In some embodiments, a downlink resource grid may be used for downlinktransmissions from an eNB 104 to a UE 102, while uplink transmissionfrom the UE 102 to the eNB 104 may utilize similar techniques. In someembodiments, a downlink resource grid may be used for downlinktransmissions from a gNB 105 to a UE 102, while uplink transmission fromthe UE 102 to the gNB 105 may utilize similar techniques. The grid maybe a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid correspond toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element (RE). There are several different physical downlinkchannels that are conveyed using such resource blocks. With particularrelevance to this disclosure, two of these physical downlink channelsare the physical downlink shared channel and the physical down linkcontrol channel.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality. In someembodiments, the circuitry may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules. In some embodiments, circuitry may includelogic, at least partially operable in hardware. Embodiments describedherein may be implemented into a system using any suitably configuredhardware and/or software.

FIG. 2 illustrates a block diagram of an example machine in accordancewith some embodiments. The machine 200 is an example machine upon whichany one or more of the techniques and/or methodologies discussed hereinmay be performed. In alternative embodiments, the machine 200 mayoperate as a standalone device or may be connected (e.g., networked) toother machines. In a networked deployment, the machine 200 may operatein the capacity of a server machine, a client machine, or both inserver-client network environments. In an example, the machine 200 mayact as a peer machine in peer-to-peer (P2P) (or other distributed)network environment. The machine 200 may be a UE 102, eNB 104, gNB 105,access point (AP), station (STA), user, device, mobile device, basestation, personal computer (PC), a tablet PC, a set-top box (STB), apersonal digital assistant (PDA), a mobile telephone, a smart phone, aweb appliance, a network router, switch or bridge, or any machinecapable of executing instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein, such as cloud computing, software asa service (SaaS), other computer cluster configurations.

Examples as described herein, may include, or may operate on, logic or anumber of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operations andmay be configured or arranged in a certain manner. In an example,circuits may be arranged (e.g., internally or with respect to externalentities such as other circuits) in a specified manner as a module. Inan example, the whole or part of one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwareprocessors may be configured by firmware or software (e.g.,instructions, an application portion, or an application) as a modulethat operates to perform specified operations. In an example, thesoftware may reside on a machine readable medium. In an example, thesoftware, when executed by the underlying hardware of the module, causesthe hardware to perform the specified operations.

Accordingly, the term “module” is understood to encompass a tangibleentity, be that an entity that is physically constructed, specificallyconfigured (e.g., hardwired), or temporarily (e.g., transitorily)configured (e.g., programmed) to operate in a specified manner or toperform part or all of any operation described herein. Consideringexamples in which modules are temporarily configured, each of themodules need not be instantiated at any one moment in time. For example,where the modules comprise a general-purpose hardware processorconfigured using software, the general-purpose hardware processor may beconfigured as respective different modules at different times. Softwaremay accordingly configure a hardware processor, for example, toconstitute a particular module at one instance of time and to constitutea different module at a different instance of time.

The machine (e.g., computer system) 200 may include a hardware processor202 (e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 204 and a static memory 206, some or all of which may communicatewith each other via an interlink (e.g., bus) 208. The machine 200 mayfurther include a display unit 210, an alphanumeric input device 212(e.g., a keyboard), and a user interface (UI) navigation device 214(e.g., a mouse). In an example, the display unit 210, input device 212and UI navigation device 214 may be a touch screen display. The machine200 may additionally include a storage device (e.g., drive unit) 216, asignal generation device 218 (e.g., a speaker), a network interfacedevice 220, and one or more sensors 221, such as a global positioningsystem (GPS) sensor, compass, accelerometer, or other sensor. Themachine 200 may include an output controller 228, such as a serial(e.g., universal serial bus (USB), parallel, or other wired or wireless(e.g., infrared (IR), near field communication (NFC), etc.) connectionto communicate or control one or more peripheral devices (e.g., aprinter, card reader, etc.).

The storage device 216 may include a machine readable medium 222 onwhich is stored one or more sets of data structures or instructions 224(e.g., software) embodying or utilized by any one or more of thetechniques or functions described herein. The instructions 224 may alsoreside, completely or at least partially, within the main memory 204,within static memory 206, or within the hardware processor 202 duringexecution thereof by the machine 200. In an example, one or anycombination of the hardware processor 202, the main memory 204, thestatic memory 206, or the storage device 216 may constitute machinereadable media. In some embodiments, the machine readable medium may beor may include a non-transitory computer-readable storage medium. Insome embodiments, the machine readable medium may be or may include acomputer-readable storage medium.

While the machine readable medium 222 is illustrated as a single medium,the term “machine readable medium” may include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions 224. The term “machine readable medium” may include anymedium that is capable of storing, encoding, or carrying instructionsfor execution by the machine 200 and that cause the machine 200 toperform any one or more of the techniques of the present disclosure, orthat is capable of storing, encoding or carrying data structures used byor associated with such instructions. Non-limiting machine readablemedium examples may include solid-state memories, and optical andmagnetic media. Specific examples of machine readable media may include:non-volatile memory, such as semiconductor memory devices (e.g.,Electrically Programmable Read-Only Memory (EPROM), ElectricallyErasable Programmable Read-Only Memory (EEPROM)) and flash memorydevices; magnetic disks, such as internal hard disks and removabledisks; magneto-optical disks: Random Access Memory (RAM); and CD-ROM andDVD-ROM disks. In some examples, machine readable media may includenon-transitory machine readable media. In some examples, machinereadable media may include machine readable media that is not atransitory propagating signal.

The instructions 224 may further be transmitted or received over acommunications network 226 using a transmission medium via the networkinterface device 220 utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as Wi-Fi®, IEEE 802.16 family ofstandards known as WiMax®), IEEE 802.15.4 family of standards, a LongTerm Evolution (LTE) family of standards, a Universal MobileTelecommunications System (UMTS) family of standards, peer-to-peer (P2P)networks, among others. In an example, the network interface device 220may include one or more physical jacks (e.g., Ethernet, coaxial, orphone jacks) or one or more antennas to connect to the communicationsnetwork 226. In an example, the network interface device 220 may includea plurality of antennas to wirelessly communicate using at least one ofsingle-input multiple-output (SIMO), multiple-input multiple-output(MIMO), or multiple-input single-output (MISO) techniques. In someexamples, the network interface device 220 may wirelessly communicateusing Multiple User MIMO techniques. The term “transmission medium”shall be taken to include any intangible medium that is capable ofstoring, encoding or carrying instructions for execution by the machine200, and includes digital or analog communications signals or otherintangible medium to facilitate communication of such software.

FIG. 3 illustrates a user device in accordance with some aspects. Insome embodiments, the user device 30X) may be a mobile device. In someembodiments, the user device 300 may be or may be configured to operateas a User Equipment (UE). In some embodiments, the user device 300 maybe arranged to operate in accordance with a new radio (NR) protocol. Insome embodiments, the user device 300 may be arranged to operate inaccordance with a Third Generation Partnership Protocol (3GPP) protocol.The user device 300 may be suitable for use as a UE 102 as depicted inFIG. 1, in some embodiments. It should be noted that in someembodiments, a UE, an apparatus of a UE, a user device or an apparatusof a user device may include one or more of the components shown in oneor more of FIGS. 2, 3, and 5. In some embodiments, such a UE, userdevice and/or apparatus may include one or more additional components.

In some aspects, the user device 300 may include an applicationprocessor 305, baseband processor 310 (also referred to as a basebandmodule), radio front end module (RFEM) 315, memory 320, connectivitymodule 325, near field communication (NFC) controller 330, audio driver335, camera driver 340, touch screen 345, display driver 350, sensors355, removable memory 360, power management integrated circuit (PMIC)365 and smart battery 370. In some aspects, the user device 300 may be aUser Equipment (UE).

In some aspects, application processor 305 may include, for example, oneor more CPU cores and one or more of cache memory, low drop-out voltageregulators (LDOs), interrupt controllers, serial interfaces such asserial peripheral interface (SPI), inter-integrated circuit (I²C) oruniversal programmable serial interface module, real time clock (RTC),timer-counters including interval and watchdog timers, general purposeinput-output (IO), memory card controllers such as securedigital/multi-media card (SD/MMC) or similar, universal serial bus (USB)interfaces, mobile industry processor interface (MIPI) interfaces andJoint Test Access Group (JTAG) test access ports.

In some aspects, baseband module 310 may be implemented, for example, asa solder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board,and/or a multi-chip module containing two or more integrated circuits.

FIG. 4 illustrates a base station in accordance with some aspects. Insome embodiments, the base station 400 may be or may be configured tooperate as an Evolved Node-B (eNB). In some embodiments, the basestation 400 may be or may be configured to operate as a GenerationNode-B (gNB). In some embodiments, the base station 400 may be arrangedto operate in accordance with a new radio (NR) protocol. In someembodiments, the base station 400 may be arranged to operate inaccordance with a Third Generation Partnership Protocol (3GPP) protocol.It should be noted that in some embodiments, the base station 400 may bea stationary non-mobile device. The base station 400 may be suitable foruse as an eNB 104 as depicted in FIG. 1, in some embodiments. The basestation 400 may be suitable for use as a gNB 105 as depicted in FIG. 1,in some embodiments. It should be noted that in some embodiments, aneNB, an apparatus of an eNB, a gNB, an apparatus of a gNB, a basestation and/or an apparatus of a base station may include one or more ofthe components shown in one or more of FIGS. 2, 4, and 5. In someembodiments, such an eNB, gNB, base station and/or apparatus may includeone or more additional components.

FIG. 4 illustrates a base station or infrastructure equipment radio head400 in accordance with an aspect. The base station 400 may include oneor more of application processor 405, baseband modules 410, one or moreradio front end modules 415, memory 420, power management circuitry 425,power tee circuitry 430, network controller 435, network interfaceconnector 440, satellite navigation receiver module 445, and userinterface 450. In some aspects, the base station 400 may be an EvolvedNode-B (eNB), which may be arranged to operate in accordance with a 3GPPprotocol, new radio (NR) protocol and/or Fifth Generation (5G) protocol.In some aspects, the base station 400 may be a generation Node-B (gNB),which may be arranged to operate in accordance with a 3GPP protocol, newradio (NR) protocol and/or Fifth Generation (5G) protocol.

In some aspects, application processor 405 may include one or more CPUcores and one or more of cache memory, low drop-out voltage regulators(LDOs), interrupt controllers, serial interfaces such as SPI, I²C oruniversal programmable serial interface module, real time clock (RTC),timer-counters including interval and watchdog timers, general purposeIO, memory card controllers such as SD/MMC or similar, USB interfaces,MIPI interfaces and Joint Test Access Group (JTAG) test access ports.

In some aspects, baseband processor 410 may be implemented, for example,as a solder-down substrate including one or more integrated circuits, asingle packaged integrated circuit soldered to a main circuit board or amulti-chip module containing two or more integrated circuits.

In some aspects, memory 420 may include one or more of volatile memoryincluding dynamic random access memory (DRAM) and/or synchronous dynamicrandom access memory (SDRAM), and nonvolatile memory (NVM) includinghigh-speed electrically erasable memory (commonly referred to as Flashmemory), phase change random access memory (PRAM), magneto-resistiverandom access memory (MRAM) and/or a three-dimensional cross-pointmemory. Memory 420 may be implemented as one or more of solder downpackaged integrated circuits, socketed memory modules and plug-in memorycards.

In some aspects, power management integrated circuitry 425 may includeone or more of voltage regulators, surge protectors, power alarmdetection circuitry and one or more backup power sources such as abattery or capacitor. Power alarm detection circuitry may detect one ormore of brown out (under-voltage) and surge (over-voltage) conditions.

In some aspects, power tee circuitry 430 may provide for electricalpower drawn from a network cable to provide both power supply and dataconnectivity to the base station 400 using a single cable. In someaspects, network controller 435 may provide connectivity to a networkusing a standard network interface protocol such as Ethernet. Networkconnectivity may be provided using a physical connection which is one ofelectrical (commonly referred to as copper interconnect), optical orwireless.

In some aspects, satellite navigation receiver module 445 may includecircuitry to receive and decode signals transmitted by one or morenavigation satellite constellations such as the global positioningsystem (GPS), Globalnaya Navigatsionnaya Sputnikovaya Sistema (GLONASS),Galileo and/or BeiDou. The receiver 445 may provide data to applicationprocessor 405 which may include one or more of position data or timedata. Application processor 405 may use time data to synchronizeoperations with other radio base stations. In some aspects, userinterface 450 may include one or more of physical or virtual buttons,such as a reset button, one or more indicators such as light emittingdiodes (LEDs) and a display screen.

FIG. 5 illustrates an exemplary communication circuitry according tosome aspects. Circuitry 500) is alternatively grouped according tofunctions. Components as shown in 500 are shown here for illustrativepurposes and may include other components not shown here in FIG. 5. Insome aspects, the communication circuitry 500 may be used for millimeterwave communication, although aspects are not limited to millimeter wavecommunication. Communication at any suitable frequency may be performedby the communication circuitry 500 in some aspects.

It should be noted that a device, such as a UE 102, eNB 104, gNB 105,the user device 300, the base station 400, the machine 200 and/or otherdevice may include one or more components of the communication circuitry500, in some aspects.

The communication circuitry 500 may include protocol processingcircuitry 505, which may implement one or more of medium access control(MAC), radio link control (RLC), packet data convergence protocol(PDCP), radio resource control (RRC) and non-access stratum (NAS)functions. Protocol processing circuitry 505 may include one or moreprocessing cores (not shown) to execute instructions and one or morememory structures (not shown) to store program and data information.

The communication circuitry 500 may further include digital basebandcircuitry 510, which may implement physical layer (PHY) functionsincluding one or more of hybrid automatic repeat request (HARQ)functions, scrambling and/or descrambling, coding and/or decoding, layermapping and/or de-mapping, modulation symbol mapping, received symboland/or bit metric determination, multi-antenna port pre-coding and/ordecoding which may include one or more of space-time, space-frequency orspatial coding, reference signal generation and/or detection, preamblesequence generation and/or decoding, synchronization sequence generationand/or detection, control channel signal blind decoding, and otherrelated functions.

The communication circuitry 500 may further include transmit circuitry515, receive circuitry 520 and/or antenna array circuitry 530. Thecommunication circuitry 500 may further include radio frequency (RF)circuitry 525. In an aspect of the disclosure, RF circuitry 525 mayinclude multiple parallel RF chains for one or more of transmit orreceive functions, each connected to one or more antennas of the antennaarray 530.

In an aspect of the disclosure, protocol processing circuitry 505 mayinclude one or more instances of control circuitry (not shown) toprovide control functions for one or more of digital baseband circuitry510, transmit circuitry 515, receive circuitry 520, and/or radiofrequency circuitry 525

In some embodiments, processing circuitry may perform one or moreoperations described herein and/or other operation(s). In a non-limitingexample, the processing circuitry may include one or more componentssuch as the processor 202, application processor 305, baseband module310, application processor 405, baseband module 410, protocol processingcircuitry 505, digital baseband circuitry 510, similar component(s)and/or other component(s).

In some embodiments, a transceiver may transmit one or more elements(including but not limited to those described herein) and/or receive oneor more elements (including but not limited to those described herein).In a non-limiting example, the transceiver may include one or morecomponents such as the radio front end module 315, radio front endmodule 415, transmit circuitry 515, receive circuitry 520, radiofrequency circuitry 525, similar component(s) and/or other component(s).

One or more antennas (such as 230, 312, 412, 530 and/or others) maycomprise one or more directional or omnidirectional antennas, including,for example, dipole antennas, monopole antennas, patch antennas, loopantennas, microstrip antennas or other types of antennas suitable fortransmission of RF signals. In some multiple-input multiple-output(MIMO) embodiments, one or more of the antennas (such as 230, 312, 412,530 and/or others) may be effectively separated to take advantage ofspatial diversity and the different channel characteristics that mayresult.

In some embodiments, the UE 102, eNB 104, gNB 105, user device 300, basestation 400, machine 200 and/or other device described herein may be amobile device and/or portable wireless communication device, such as apersonal digital assistant (PDA), a laptop or portable computer withwireless communication capability, a web tablet, a wireless telephone, asmartphone, a wireless headset, a pager, an instant messaging device, adigital camera, an access point, a television, a wearable device such asa medical device (e.g., a heart rate monitor, a blood pressure monitor,etc.), or other device that may receive and/or transmit informationwirelessly. In some embodiments, the UE 102, eNB 104, gNB 105, userdevice 300, base station 400, machine 200 and/or other device describedherein may be configured to operate in accordance with 3GPP standards,although the scope of the embodiments is not limited in this respect. Insome embodiments, the UE 102, eNB 104, gNB 105, user device 300, basestation 400, machine 200 and/or other device described herein may beconfigured to operate in accordance with new radio (NR) standards,although the scope of the embodiments is not limited in this respect. Insome embodiments, the UE 102, eNB 104, gNB 105, user device 300, basestation 400, machine 200 and/or other device described herein may beconfigured to operate according to other protocols or standards,including IEEE 802.11 or other IEEE standards. In some embodiments, theUE 102, eNB 104, gNB 105, user device 300, base station 400, machine 200and/or other device described herein may include one or more of akeyboard, a display, a non-volatile memory port, multiple antennas, agraphics processor, an application processor, speakers, and other mobiledevice elements. The display may be an LCD screen including a touchscreen.

Although the UE 102, eNB 104, gNB 105, user device 300, base station400, machine 200 and/or other device described herein may each beillustrated as having several separate functional elements, one or moreof the functional elements may be combined and may be implemented bycombinations of software-configured elements, such as processingelements including digital signal processors (DSPs), and/or otherhardware elements. For example, some elements may comprise one or moremicroprocessors, DSPs, field-programmable gate arrays (FPGAs),application specific integrated circuits (ASICs), radio-frequencyintegrated circuits (RFICs) and combinations of various hardware andlogic circuitry for performing at least the functions described herein.In some embodiments, the functional elements may refer to one or moreprocesses operating on one or more processing elements.

Embodiments may be implemented in one or a combination of hardware,firmware and software. Embodiments may also be implemented asinstructions stored on a computer-readable storage device, which may beread and executed by at least one processor to perform the operationsdescribed herein. A computer-readable storage device may include anynon-transitory mechanism for storing information in a form readable by amachine (e.g., a computer). For example, a computer-readable storagedevice may include read-only memory (ROM), random-access memory (RAM),magnetic disk storage media, optical storage media, flash-memorydevices, and other storage devices and media. Some embodiments mayinclude one or more processors and may be configured with instructionsstored on a computer-readable storage device.

It should be noted that in some embodiments, an apparatus used by the UE102, eNB 104, gNB 105, machine 200, user device 300 and/or base station400 may include various components shown in FIGS. 2-5. Accordingly,techniques and operations described herein that refer to the UE 102 maybe applicable to an apparatus of a UE. In addition, techniques andoperations described herein that refer to the eNB 104 may be applicableto an apparatus of an eNB. In addition, techniques and operationsdescribed herein that refer to the gNB 105 may be applicable to anapparatus of a gNB.

FIG. 6 illustrates an example of a radio frame structure in accordancewith some embodiments. FIGS. 7A and 7B illustrate example frequencyresources in accordance with some embodiments. In references herein,“FIG. 7” may include FIG. 7A and FIG. 7B. It should be noted that theexamples shown in FIGS. 6-7 may illustrate some or all of the conceptsand techniques described herein in some cases, but embodiments are notlimited by the examples. For instance, embodiments are not limited bythe name, number, type, size, ordering, arrangement and/or other aspectsof the time resources, symbol periods, frequency resources, PRBs andother elements as shown in FIGS. 6-7. Although some of the elementsshown in the examples of FIGS. 6-7 may be included in a 3GPP LTEstandard, 5G standard, NR standard and/or other standard, embodimentsare not limited to usage of such elements that are included instandards.

An example of a radio frame structure that may be used in some aspectsis shown in FIG. 6. In this example, radio frame 600 has a duration of10 ms. Radio frame 600 is divided into slots 602 each of duration 0.5ms, and numbered from 0 to 19. Additionally, each pair of adjacent slots602 numbered 2i and 2i+1, where i is an integer, is referred to as asubframe 601.

In some aspects using the radio frame format of FIG. 6, each subframe601 may include a combination of one or more of downlink controlinformation, downlink data information, uplink control information anduplink data information, sidelink control and data information. Thecombination of information types and direction may be selectedindependently for each subframe 602.

Referring to FIGS. 7A and 7B, in some aspects, a sub-component of atransmitted signal consisting of one subcarrier in the frequency domainand one symbol interval in the time domain may be termed a resourceelement. Resource elements may be depicted in a grid form as shown inFIG. 7A and FIG. 7B.

In some aspects, illustrated in FIG. 7A, resource elements may begrouped into rectangular resource blocks 700 consisting of 12subcarriers in the frequency domain and the P symbols in the timedomain, where P may correspond to the number of symbols contained in oneslot, and may be 6, 7, or any other suitable number of symbols.

In some alternative aspects, illustrated in FIG. 7B, resource elementsmay be grouped into resource blocks 700 consisting of 12 subcarriers (asindicated by 702) in the frequency domain and one symbol in the timedomain. In the depictions of FIG. 7A and FIG. 7B, each resource element705 may be indexed as (k, l) where k is the index number of subcarrier,in the range 0 to N.M−1 (as indicated by 703), where N is the number ofsubcarriers in a resource block, and M is the number of resource blocksspanning a component carrier in the frequency domain.

In accordance with some embodiments, the gNB 105 may allocate a resourcepool of physical resource blocks (PRBs) and sub-frames forvehicle-to-vehicle (V2V) sidelink transmissions. The gNB 105 mayreceive, from a UE 102, an uplink control message that indicates thatthe UE 102 requests a V2V sidelink transmission of a prioritizedmessage. The eNB 104 may select, for the V2V sidelink transmission ofthe prioritized message, one or more PRBs of the resource pool and oneor more sub-frames of the resource pool. The gNB 105 may transmit, tothe UE 102 and to other UEs 102, a downlink control message thatindicates: the selected PRBs, the selected sub-frames, and that theother UEs 102 are to mute sidelink transmissions in the selected PRBs inthe selected sub-frames to enable the V2V sidelink transmission of theprioritized message. These embodiments are described in more detailbelow.

FIG. 8 illustrates the operation of a method of communication inaccordance with some embodiments. FIG. 9 illustrates the operation ofanother method of communication in accordance with some embodiments. Indescribing the methods 800 and 900, reference may be made to one or moreof FIGS. 1-13, although it is understood that the methods 800 and 900may be practiced with any other suitable systems, interfaces andcomponents. In some cases, descriptions herein of one or more of theconcepts, operations and/or techniques regarding one of the methodsdescribed herein (800, 900 and/or other) may be applicable to at leastone of the other methods described herein (800, 900 and/or other).

Some embodiments of the method 800 may include additional operations incomparison to what is illustrated in FIG. 8, including but not limitedto operations described herein. Some embodiments of the method 800 maynot necessarily include all of the operations shown in FIG. 8. Inaddition, embodiments of the method 800 are not necessarily limited tothe chronological order that is shown in FIG. 8. In some embodiments, agNB 105 may perform one or more operations of the method 800, butembodiments are not limited to performance of the method 800) and/oroperations of it by the gNB 105. Accordingly, although references may bemade to performance of one or more operations of the method 800 by thegNB 105 in descriptions herein, it is understood that the eNB 104 and/orUE 102 may perform one or more operations that may be the same as,similar to and/or reciprocal to one or more of the operations of themethod 800, in some embodiments.

Some embodiments of the method 900 may include additional operations incomparison to what is illustrated in FIG. 9, including but not limitedto operations described herein. Some embodiments of the method 900 maynot necessarily include all of the operations shown in FIG. 9. Inaddition, embodiments of the method 900 are not necessarily limited tothe chronological order that is shown in FIG. 9. In some embodiments, aUE 102 may perform one or more operations of the method 900, butembodiments are not limited to performance of the method 900 and/oroperations of it by the UE 102. Accordingly, although references may bemade to performance of one or more operations of the method 900 by theUE 102 in descriptions herein, it is understood that the eNB 104 and/orgNB 105 may perform one or more operations that may be the same as,similar to and/or reciprocal to one or more of the operations of themethod 900, in some embodiments.

While the methods 800 and 900 and other methods described herein mayrefer to eNBs 104, gNBs 105 or UEs 102 operating in accordance with 3GPPstandards, 5G standards. NR standards and/or other standards,embodiments of those methods are not limited to just those eNBs 104,gNBs 105 or UEs 102 and may also be practiced on other devices, such asa Wi-Fi access point (AP) or user station (STA). In addition, themethods 800, 900 and other methods described herein may be practiced bywireless devices configured to operate in other suitable types ofwireless communication systems, including systems configured to operateaccording to various IEEE standards such as IEEE 802.11. The methods800, 900 and other methods described herein may also be applicable to anapparatus of a UE 102, an apparatus of an eNB 104, an apparatus of a gNB105 and/or an apparatus of another device described above.

It should also be noted that embodiments are not limited by referencesherein (such as in descriptions of the methods 800, 900 and/or otherdescriptions herein) to transmission, reception and/or exchanging ofelements such as frames, messages, requests, indicators, signals orother elements. In some embodiments, such an element may be generated,encoded or otherwise processed by processing circuitry (such as by abaseband processor included in the processing circuitry) fortransmission. The transmission may be performed by a transceiver orother component, in some cases. In some embodiments, such an element maybe decoded, detected or otherwise processed by the processing circuitry(such as by the baseband processor). The element may be received by atransceiver or other component, in some cases. In some embodiments, theprocessing circuitry and the transceiver may be included in a sameapparatus. The scope of embodiments is not limited in this respect,however, as the transceiver may be separate from the apparatus thatcomprises the processing circuitry, in some embodiments.

One or more of the messages described herein may be included in astandard and/or radio-protocol, including but not limited to ThirdGeneration Partnership Project (3GPP), 3GPP Long Term Evolution (LTE),Fourth Generation (4G), Fifth Generation (5G), New Radio (NR) and/orother. The scope of embodiments is not limited to usage of elements thatare included in standards, however.

At operation 805, the gNB 105 may allocate a resource pool forvehicle-to-vehicle (V2V) sidelink transmissions. In some embodiments,the gNB 105 may allocate the resource pool for gNB-controlled (includingbut not limited to mode-3) vehicle-to-vehicle (V2V) sidelinktransmissions in accordance with resource selection by the gNB 105. Insome embodiments, the gNB 105 may allocate the resource pool forUE-autonomous (including but not limited to mode-4) V2V sidelinktransmissions in accordance with autonomous resource selection by UEs102. In some embodiments, the gNB 105 may allocate the resource pool fora combination of mode-3 V2V sidelink transmissions and mode-4 V2Vsidelink transmissions.

In some embodiments, the resource pool may include time resource and/orfrequency resources. In a non-limiting example, the resource pool mayinclude one or more physical resource blocks (PRBs) or frequencysub-channels and one or more sub-frames in time. In some embodiments,the resource pool may include contiguous frequency resources and/orPRBs, although the scope of embodiments is not limited in this respect.In some embodiments, the resource pool may include contiguous timeresources and/or sub-frames, although the scope of embodiments is notlimited in this respect.

It should be noted that descriptions herein of some operations and/ortechniques may refer to PRBs/sub-channels and sub-frames, but suchreferences are not limiting. In some embodiments, other time resourcesand/or frequency resources may be used in one or more of thoseoperations and/or techniques.

At operation 810, the gNB 105 may transmit a downlink control messagethat indicates the resource pool. In some embodiments, the downlinkcontrol message may indicate PRBs and/or sub-frames of the resourcepool, although the scope of embodiments is not limited in this respect.Any suitable information that indicates the resource pool may beincluded in the downlink control message.

At operation 815, the gNB 105 may receive an uplink control message thatindicates that the UE requests a V2V sidelink transmission of aprioritized message. In a non-limiting example, the prioritized messagemay be an emergency message. In another non-limiting example, theprioritized message may be of a priority level that is “high” in somesense, such as: relatively high, higher than a threshold, higher than anaverage priority and/or other.

In some embodiments, the uplink control message may indicate one or moreof: a transmission period for the V2V sidelink transmission of theprioritized message, a number of PRBs for the V2V sidelink transmissionof the prioritized message, a buffer status report and/or other.

In some embodiments, the uplink control message may be included in aphysical uplink shared channel (PUSCH). In some embodiments, the uplinkcontrol message may be a physical uplink control channel (PUCCH). ThePUSCH and/or PUCCH may be included in a 3GPP standard, in someembodiments. It should be noted that embodiments are not limited tousage of the path switch trigger message in this operation and/or otheroperations described herein, as any suitable messages may be used.

At operation 820, the gNB 105 may select resources for a V2V sidelinktransmission. In some embodiments, the gNB 105 may select resources forthe V2V sidelink transmission of the prioritized message. In someembodiments, the gNB 105 may select, for the V2V sidelink transmissionof the prioritized message: one or more PRBs of the resource pool, oneor more sub-frames of the resource pool or a combination thereof. Insome embodiments, the gNB 105 may select resources that may notnecessarily be contiguous in time and frequency. For instance, theresources may include first PRBs in a first symbol or subframe andsecond PRBs in a second symbol or subframe, and the first PRBs may bedifferent from the second PRBs.

In some embodiments, the gNB 105 may select the resources (such as PRBsand sub-frames) for the V2V sidelink transmission of the prioritizedmessage based at least partly on information included in the uplinkcontrol message. In some embodiments, the gNB 105 may select theresources (such as PRBs and sub-frames) for the V2V sidelinktransmission of the prioritized message based at least partly on channelsense measurements (such as those described regarding operation 940). Insome embodiments, one or more other factors may be used by the gNB 105for the selection of resources, in addition to or instead of the factorsdescribed above.

It should be noted that one or more operations of methods describedherein (such as 800), 900 and/or others) may be described for cases inwhich a V2V sidelink transmission of prioritized message is to be used.Such operations may include, but are not limited to, resource selection,indication of selected resources and/or others. However, suchdescriptions are not limiting, as one or more of those operations may beapplicable to cases in which V2V sidelink transmissions are used formessages that may not necessarily be prioritized messages, in someembodiments.

At operation 825, the gNB 105 may transmit a downlink control messagethat indicates that other UEs 102 are to mute transmissions in theselected PRBs in the selected sub-frame. In some embodiments, thedownlink control message may further indicate one or more of: theselected PRBs, the selected sub-frames, a time duration for which theother UEs 102 are to mute the sidelink transmissions in the selectedPRBs in the selected sub-frames and/or other information.

In some embodiments, the gNB 105 may transmit the downlink controlmessage to the UE 102. In some embodiments, the gNB 105 may transmit thedownlink control message to other UEs 102. In some embodiments, the gNB105 may transmit the downlink control message to the UE 102 and to otherUEs 102.

In a non-limiting example, the downlink control message may be a mediumaccess control (MAC) control element (CE) included in a physicaldownlink shared channel (PDSCH). In another non-limiting example, thedownlink control message may be a physical downlink control channel(PDCCH). The PDCCH may include a downlink control information (DCI) thatindicates the selected resources (such as selected PRBs, selectedsub-frames and/or other). In another non-limiting example, the downlinkcontrol message may be a broadcast system information block (SIB).

At operation 830, the gNB 105 may transmit a downlink control messagethat indicates one or more parameters for one or more channel sensemeasurements by UEs 102. Example parameters for the channel sensemeasurements include, but are not limited to: a number of PRBs for themeasurements, a number of sub-frames for the measurements and/or other.

In some embodiments, the channel sense measurement may be a sidelinkreceived signal strength indicator (S-RSSI). Other measurements may beused, including but not limited to a signal-to-noise ratio (SNR), areference signal received power (RSRP), a reference signal receivedquality (RSRQ), a channel busy ratio (CBR), or measurements to reportcandidate subset of resources for selection or subset of resources thatshould not be used (unavailable/excluded) for transmission and/or other.

At operation 835, the gNB 105 may receive an uplink control message thatindicates the one or more channel sense measurements. Any suitable typeof uplink control message, such as a PUCCH, PUSCH and/or other, may beused.

At operation 840, the gNB 105 may select, based at least partly on theone or more channel sense measurements, one or more resources for a V2Vsidelink transmission. In some embodiments, the gNB 105 may transmit adownlink control message (including but not limited to messagesdescribed herein regarding operation 825) to indicate the resourcesselected at operation 840.

In a non-limiting example of resource selection, the channel sensemeasurement may be related to first resources of the resource pool. ThegNB 105 may select second resources of the resource pool for the mode-3V2V sidelink transmission. The gNB 105 may determine, based at leastpartly on the channel sense measurement, whether the first resources areunavailable for mode-3 V2V sidelink transmissions. If it is determinedthat the first resources are unavailable for mode-3 V2V sidelinktransmissions, the gNB 105 may select the second resources fromcandidate resources that exclude the first resources.

In some embodiments, the gNB 105 may be arranged to operate inaccordance with a Third Generation Partnership Project (3GPP) protocol.In some embodiments, the gNB 105 may be configured for mode-3 operation,wherein the gNB 105 is to select time resources and/or frequencyresources (such as PRBs and sub-frames of the resource pool) for a V2Vsidelink transmission. In some embodiments, uplink control messages maybe received by the gNB 105 over an uplink Uu interface and downlinkcontrol messages may be transmitted by the gNB 105 over a downlink Uuinterface.

In some embodiments, the gNB 105 may transmit downlink control signalingto instruct UEs 102 to perform one or more of: monitor one or moresidelink resource pools; sense the sidelink resource pools; performradio-layer measurements within the sidelink resource pools; determinecandidate resources of the sidelink resource pools that are availablefor sidelink transmission (for instance, the best M candidate resourcesmay be determined, wherein M≥1): determine resources of the sidelinkresource pools that are to be excluded from selection for the sidelinktransmissions; determine resources of the sidelink resource pools thatare not available for the sidelink transmissions.

In some embodiments, radio-layer parameters (for the above operationsand/or other operations) may be configured by the gNB 105 usingsignaling (including but not limited to RRC signaling) that may indicateone or more of: triggering conditions for measurement and/or reportingof results to the gNB 105; a pre-configured reporting format; apre-defined reporting format; and/or other.

In some embodiments, triggering conditions may be based on one or morethresholds for measurements related to detection of sidelinktransmissions. Example measurements include, but are not limited to,received power and reference signal received power (RSRP). For instance,if a measurement exceeds a threshold, a report may be triggered. In someembodiments, triggering conditions may be based on one or morethresholds for priority levels of detected sidelink signals. Forinstance, if the priority level of a detected signal is above athreshold, a report may be triggered. A combination of the above (and/orother) may be used, in some embodiments. For instance, a report may betriggered if a priority of a detected sidelink transmission is greaterthan a first threshold and if a measurement (such as received power,RSRP and/or other) of the detected sidelink transmission is greater thana second threshold, a report may be triggered.

In some embodiments, a pre-configured reporting format and/orpre-defined reporting format may include one or more of: a candidateresource set: a subset of the best selected resources from candidateresource set recommended for transmission; resources that should not beused for scheduling sidelink transmissions: resources for which it isrecommended to refrain from allocation for scheduling of sidelinktransmissions; and/or other. In a non-limiting example, the report maybe sent over PUCCH or PUSCH in the form of MAC CE or other types of ULcontrol signaling.

In some embodiments, an apparatus of a gNB 105 may comprise memory. Thememory may be configurable to store information identifying selectedPRBs and selected sub-frames. The memory may store one or more otherelements and the apparatus may use them for performance of one or moreoperations. The apparatus may include processing circuitry, which mayperform one or more operations (including but not limited tooperation(s) of the method 800 and/or other methods described herein).The processing circuitry may include a baseband processor. The basebandcircuitry and/or the processing circuitry may perform one or moreoperations described herein, including but not limited to selection ofresources for the V2V sidelink transmission of the prioritized message.The apparatus of the gNB 105 may include a transceiver to receive anuplink control message and to transmit a downlink control message. Thetransceiver may transmit and/or receive other blocks, messages and/orother elements.

At operation 905, the UE 102 may receive a downlink control message thatindicates a resource pool for V2V sidelink transmission.

At operation 910, the UE 102 may determine that the UE is to perform aV2V sidelink transmission of a prioritized message. In a non-limitingexample, the UE 102 may determine that the prioritized message is to betransmitted over the V2V sidelink based at least partly on an indicatorgenerated by an application layer of the UE 102.

At operation 915, the UE 102 may select resources for the V2V sidelinktransmission of the prioritized message. In some embodiments, the UE 102may select one or more PRB and one or more sub-frames for the V2Vsidelink transmission of the prioritized message.

At operation 920, the UE 102 may transmit a sidelink control messagethat indicates that other UEs 102 are to mute sidelink transmissions inthe selected/indicated set of PRBs and sub-frames. In some embodiments,the sidelink control message may further indicate one or more of: theselected PRBs, the selected sub-frames, a time duration for which theother UEs 102 are to mute the sidelink transmissions in the selectedPRBs in the selected sub-frames and/or other information.

In a non-limiting example, the sidelink control message may be includedin a physical sidelink shared channel (PSSCH). In another non-limitingexample, the sidelink control message may be a physical sidelink controlchannel (PSCCH) that includes a sidelink control information (SCI) thatincludes the selected resources (such as the selected PRBs and theselected sub-frames). Embodiments are not limited to these examples, asother types of sidelink control messages may be used.

At operation 925, the UE 102 may transmit the prioritized message in theselected resources.

At operation 930, the UE 102 may receive a downlink control message thatindicates one or more parameter for one or more channel sensemeasurements by UEs 102. At operation 935, the UE 102 may determine theone or more channel sense measurements. At operation 940, the UE 102 maytransmit an uplink control message that indicates the one or morechannel sense measurements.

In some embodiments, one or more of operations 930-940 may be performedin accordance with mode-3 operation. In some embodiments, the UE 102 mayoperate in accordance with mode-4 operation and may not necessarilyperform one or more of operations 930-940. For instance, channel sensingin accordance with mode-4 operation may be performed locally by the UE102 without an exchange of messages (such as from the gNB 105) thatindicate such measurements.

In some embodiments, the UE 102 may be arranged to operate in accordancewith a Third Generation Partnership Project (3GPP) protocol. In someembodiment, the UE 102 may be configured for mode-4 operation, whereinthe UE 102 is to select the resources (such as the PRBs and thesub-frames) for V2V sidelink transmissions.

It should be noted that some embodiment may not necessarily include alloperations shown in FIG. 9. For instance, if the UE 102 operates inaccordance with mode-4 operation, the UE 102 may not necessarily performone or more of operations 930-940.

In some embodiments, an apparatus of a UE 102 may comprise memory. Thememory may be configurable to store at least a portion of theprioritized message. The memory may store one or more other elements andthe apparatus may use them for performance of one or more operations.The apparatus may include processing circuitry, which may perform one ormore operations (including but not limited to operation(s) of the method900 and/or other methods described herein). The processing circuitry mayinclude a baseband processor. The baseband circuitry and/or theprocessing circuitry may perform one or more operations describedherein, including but not limited to selection of resources for a V2Vtransmission. The apparatus of the UE 102 may include a transceiver totransmit the sidelink control message. The transceiver may transmitand/or receive other blocks, messages and/or other elements.

In some embodiments, techniques and/or operations described herein maybe applicable for implementation in Cellular V2X systems including LTEV2X and NR V2X technologies. In some cases, such techniques and/oroperations may enable improvements in comparison to other systems, suchas a higher reliability of high priority vehicular message transmission,a reduced V2X system reaction time and/or other.

In some V2X use cases, such as cases in which a traffic jam occurs dueto an accident and/or other event(s), a number of cars in a same areamay be relatively large. A probability of message collision for vehicleto vehicle (V2V) communication may be high in cases in which a densityof vehicles in a same geographical area is high. A communication rangeof the sidelink V2V message transmission may be reduced in these andother scenarios.

In some cases, high priority messages and/or indications may be used. Ina non-limiting example scenario, a safety car (police, medical and/orother) may transmit emergency messages and/or indications to other cars.For instance, the safety car may indicate to other cars to switch lanesdue to emergency or align trajectory. In some embodiments, a mechanismfor transmission of “high priority” packets may be used. In someembodiments, a UE 102 (and/or other device) may indicate to one or moreother UEs 102 (and/or other devices) one or more of the following: thatthe other UEs 102 are to “mute” transmission, that the other UEs 102 areto exclude certain resources from candidate resources, that the otherUEs 102 are to stop transmission on indicated resources during a timeinterval; and/or other. These mechanisms and/or other mechanisms may beapplicable to various scenarios, including the above scenarios.

In some embodiments, a “mute” control signaling procedure (such as amute announcement/request and/or other) may be used. In some cases, sucha procedure may be used for notification of other UEs 102 to stoptransmitting in order for higher priority safety message to reachneighboring UEs 102. The higher priority safety message may betransmitted on a “muted” resource in which other transmissions are to bemuted. In some embodiments, the muted resource may be a dedicatedresource, although the scope of embodiments is not limited in thisrespect. An indication mechanism may be signaled by the gNB 105, UE 102and/or other device. The techniques described herein may be applicableto Mode-3 scenarios (in which the gNB 105 controls resource allocation),Mode-4 scenarios (in which autonomous resource allocation by one or moreUEs 102 is used) and/or other scenarios.

In some embodiments, the muted resource may be restricted to a subset ofresource blocks (RBs)/sub-channels and/or subframes. In someembodiments, the muted resource may be held/restricted for a limitedduration of time. In some embodiments, a sidelink relaying mechanism maybe used by the UE 102 for one or more of the following: to receive highpriority messages, to retransmit high priority messages to otherdevices, to disseminate information (such as a number of hops forrepetition/retransmission and/or other information) about resourcesprohibited for selection and reservation by other UEs 102; and/or otheroperation(s).

In some embodiments, a sidelink mute/reservation request may be used. Ina non-limiting example, the sidelink mute/reservation request may bebased on eNB/gNB control signaling, although the scope of embodiments isnot limited in this respect. The gNB 105 may indicate a mute request toUEs 102 based on the network command or by request from served UEs 102that request resources for high priority sidelink transmission with highreliability (for instance, mission critical traffic with low latency andhigh reliability requirements). In this scenario, it may be assumed thatUEs 102 performing V2V sidelink communication on certain frequencychannel also monitor Uu air-interface to receive commands from eNBs 104and/or gNBs 105. Different approaches are possible, including but notlimited to single cell point to multipoint (SC-PTM), multicast broadcastsingle frequency network (MBSFN), basic DL communication and/or other.

From a physical layer perspective, such an indication in the downlinkmay be signaled in a PDCCH, a PDSCH and/or or a PMCH (which will bedescribed below), although other elements may be used. In someembodiments, the gNB 105 may transmit a PDCCH that indicates a muteoperation. In some embodiments, the gNB 105 may transmit a PDSCH thatindicates a mute operation. In some embodiments, the gNB 105 maytransmit a PMCH that indicates a mute operation. Embodiments are notlimited to usage of these elements (PDCCH, PDSCH, PMCH) for indicationof the mute operation, as other elements may be used in someembodiments.

In some embodiments, including but not limited to embodiments in whichthe PDCCH is used for a mute indication, an existing DL DCI formatand/or other DL DCI format may be defined to carry physical layerindication of resources to mute sidelink transmissions. In some cases, areuse of legacy DCI formats (such as 5 or 5A in a 3GPP LTE standardand/or other format) may be a preferred design option to avoid increasein blind decoding attempts. A dedicated RNTI (such as RSRV_RNTI,MUTE_RNTI and/or other) may be allocated/configured to enable the UE 102to monitor DCI transmissions in a common search space (or group commonsearch space or CORE_SET) and to receive a mute command from the gNB105. Alternatively. V2X or SC-PTM RNTIs allocated for a common searchspace may be used.

In some embodiments, including but not limited to embodiments in whichthe PDCCH is used for a mute indication, the content of DCI formatcarrying mute information may indicate sidelink resources in which UEs102 are to drop transmissions and are to exclude these resources fromcandidate resources for selection. In some embodiments, the eNB 104/gNB105 mute command through PDCCH control signaling may look similar to asidelink grant in eNB 104 and/or gNB 105 controlled resource allocationmode. In some embodiments, the eNB 104/gNB 105 mute command throughPDCCH control signaling may comprise one or more of the following:priority information, for instance that transmissions with lowerpriority are to be muted on indicated resources and the indicatedresources are to be excluded those from candidates resources forselection; frequency resource location information, including but notlimited to a set of frequency sub-channels, sub-bands or physicalresource blocks; time resource location information, including but notlimited to a set of subframes or slots periodically occurring in time;resource reservation interval/period, including but not limited to aperiod of muted resource occasions; a mute/reservation interval, forinstance a timer configuration to indicate for how long the command issupposed to be valid (otherwise eNB 104/gNB 105 may periodically signalthis command): a sidelink resource pool ID, for instance which sidelinkresource pool should not be used for transmission, wherein thisprinciple may rely on dynamic activation/deactivation of pre-configuredsidelink resource pools available for transmission: resource allocationmode indication, for instance whether the mute command is applicable toMode-3 (eNB 104/gNB 105 controlled UEs 102) or to Mode-4 (UEs 102 usingautonomous resource selection) or both modes of operation; locationinformation, for instance an ID of geographical area/zone for which thiscommand was issued; a sidelink carrier ID, for instance an indication ofsidelink carrier or carrier set in which resources are to be muted; ahop counter for resource reservation/mute request (for instance in casesin which signaling is relayed by a UE 102, it should increment relay hopcounter); and/or other information.

In some embodiments, including but not limited to embodiments in whichthe PDCCH is used for a mute indication, the UE 102 may perform one ormore of the following behaviors. The target UE 102, upon reception ofDCI command, may be expected to mute transmission on indicated sidelinkresources and resume use of these resources upon commandcompletion/expiration or additional eNB/gNB signaling to release theseresources. The target UE 102 may be determined by RNTI, geographicallocation information and/or other information. The target UE 102, ifconfigured, may relay this information on sidelink so that UEs 102 areaware about the mute operation on the subset of sidelink resources. Thetarget UE 102 may use SCI signaling in PSCCH, MAC CE delivered throughPSSCH transmission and/or other element for the relay. The UE 102 mayrequest the gNB 105 to send this mute command and provide a UE 102report with assistance information including one or more of: a period oftransmission, an amount of frequency resources or buffer status report,priority information, location information, and/or other information.The UE 102 may be preconfigured through RRC signaling with systemparameters to execute such system behavior, such as one or more of:timer information indicating validity of command, resource pools forwhich the command is applicable, component carriers in which suchoperation may be enabled, applicable resource allocation modes, and/orother.

In some embodiments, including but not limited to embodiments in whichthe PDCCH is used for a mute indication, the eNB 104/gNB 105 may performone or more of the following behaviors. The eNB 104/gNB 105 mayconfigure UEs 102 to enable functionality of sidelink resourcemute/reservation. The eNB 104/gNB 105 may generate resource mute commandupon request from network or UEs 102 and may signal it to UEs 102 incell area and may signal it in PDCCH/PDSCH/PMCH. The eNB 104/gNB 105 maysignal these commands periodically until the mute and resourcereservation is valid. The eNB 104/gNB 105 may exchange controlinformation about muted resources with neighbor eNBs 104/gNBs 105through X2AP interface.

In some cases, a mechanism based on PDCCH indication (including but notlimited to a mechanism similar to the one described above) may provide arelatively fast system reaction time and may be used for latencycritical applications.

In some cases, including but not limited to cases in which a payloadsize of DCI is not sufficient to enable mute operation, the PDSCH may beused for the indication. This mode of operation may be implemented basedon SC-PTM framework or using unicast or group common DL transmissions,although the scope of embodiments is not limited in this respect. Insome embodiments, the indication of muted/reserved resources may reusesidelink resource pool configuration principle or sidelink grant used incase of eNB/gNB controlled resource allocation mode. In some cases,including but not limited to cases in which resource pool configurationsignaling is reused for indication of muted/reserved resources, the UE102 may use pre-configured resource pools for sidelink transmission, maydrop transmission and/or may exclude from resource selection overlappedsidelink resources.

In some embodiments, including but not limited to embodiments in whichthe PDSCH is used for a mute indication, MAC Control element (CE)(including but not limited to a V2X MAC CE) may be used for theindication. Embodiments are not limited to usage of this element for themute indication, however, as other elements may be used in someembodiments. In some embodiments, the V2X MAC CONTROL CE may betransmitted in a unicast or a broadcast mode to vehicles in a givenarea. The MAC control CE may include one or more of the following: acommand type, such as whether to mute or to release mute; priorityinformation, for instance, transmissions with lower priority onindicated resources are to be muted, the indicated resources are to beexcluded from candidates resources for selection and/or other: frequencyresource location information, such as one or more of a set of frequencysub-channels, sub-bands or physical resource blocks; a list ofidentifiers (IDs), such as destination-layer2-ids and/or other: timeresource location information, such as a set of subframes or slotsperiodically occurring in time; resource reservation interval/period,for instance a period of muted resource occasions; a mute/reservationinterval, for instance a timer configuration to indicate for how longthe command is supposed to be valid (otherwise eNB 104/gNB 105 mayperiodically signal this command); sidelink resource pool ID, forinstance which sidelink pool should not be used for transmission (thisprinciple may rely on dynamic activation/deactivation of pre-configuredsidelink resource pools available for transmission, in some cases);resource allocation mode indication, for instance whether mute commandis applicable to Mode-3 (eNB 104/gNB 105 controlled UEs 102) or toMode-4 (UEs 102 using autonomous resource selection) or both modes ofoperation; location information, for instance an ID of a geographicalarea/zone for which the mute command is, including but not limited to azone ID of a 3GPP LTE standard; a sidelink carrier ID, for instance anindication of sidelink carrier(s) and/or carrier set in which resourcesare to be muted; a hop counter for resource reservation, mute requestand/or other; and/or other information.

In some embodiments, a system information broadcast (SIB) may includeone or more of the following: a mute indication, a mute command,information related to a mute operation (including but not limited toinformation related to a mute operation that may be included in a MAC CEdescribed herein); and/or other information. In a non-limiting example,an extension of the SIB 21 and/or other SIB may be used. The SIB may bebroadcast. The SIB may be received by multiple vehicles/devices.

In some embodiments, a UE 102 may receive a MAC CE or SIB that indicatesa mute command. The UE 102 may mute transmission on indicated sidelinkresources. The UE 102 may resume usage of those resources. For instance,the UE 102 may resume usage of those resources upon command completionor based on additional eNB 104/gNB 105 signaling or based on otherevent(s).

In some embodiments, the target UE 102 may be determined by RNTI,SL-V-RNTI, geographical location information and/or other information.The target UE 102 may, if configured, relay some information about thesidelink, which may enable multiple UEs 102 to be aware about a muteoperation on the subset of sidelink resources. The target UE 102 may useSCI signaling in PSCCH, MAC CE delivered through PSSCH transmissionand/or other element for the relay. A priority of the MAC CE may beconfigured by eNB 104/gNB 105 signaling or may be pre-configured.

In some embodiments, the UE 102 may request that the gNB 105 send a mutecommand and/or a UE report with assistance information. The assistanceinformation may be related to a mute operation, such as one or more of:a period of transmission, an amount of frequency resources, a bufferstatus report, priority information, location information and/or other.

In some embodiments, the UE 102 may be preconfigured (through RRCsignaling and/or other) with system parameters to execute such systembehavior. Such information may include one or more of: timer informationindicating validity of the mute command, resource pools for which themute command is applicable, component carriers in which such operationmay be enabled, applicable resource allocation modes and/or other.

In some embodiments, including but not limited to embodiments in whichthe SIB is used for a mute indication, the eNB 104/gNB 105 may performone or more of the following behaviors. The eNB 104/gNB 105 mayconfigure UEs 102 to enable functionality of sidelink resourcemute/reservation. The eNB 104/gNB 105 may generate resource mute commandupon request from network or UEs 102 and may signal it to UEs 102 incell area and may signal it in PDCCH/PDSCH/PMCH. The eNB 104/gNB 105 maysignal these commands periodically until the mute and resourcereservation is valid. The eNB 104/gNB 105 may exchange controlinformation about muted resources with neighbor eNBs 104/gNBs 105through X2AP interface.

In some embodiments, including but not limited to embodiments in whichthe PMCH is used for a mute indication, the PMCH based indication mayassume utilization of MBMS protocols to carry information about sidelinkresource mute/reservation across multiple cells using MBSFNtransmissions. In some embodiments, a Temporary Mobile Group Identity(TMGI) may be configured for service notification related to V2X. ThisTMGI may be associated with a V2X configuration sidelink. An applicationthat handles this service may be configured with the enhance resourcereservation configuration. In some embodiments, the PMCH may include oneor more of the following: a mute indication, a mute command, informationrelated to a mute operation (including but not limited to informationrelated to a mute operation that may be included in a MAC CE describedherein); and/or other information.

In some embodiments, the UE 102 may transmit control signaling and/or anelement that includes a mute indication, a mute command, a sidelinkmute/reservation request and/or other information related to a muteoperation. Non-limiting examples of such control signaling and/orelement include a PSCCH (sidelink control) channel or PSSCH (sidelinkshared) channel.

In some embodiments, a mechanism to reserve/mute resources may beactivated upon request from application layers. The sidelink mute andresource reservation request may be carried out through different typesof sidelink signaling. For instance, upon notification from V2X stack(such as a notification that an emergency high priory message (ITS/SAEfor this message priority class) is to be sent, a notification that themedium is congested and/or a notification of another event), thecellular MAC layer may send and/or request physical layer to send amessage/element to indicate a mute operation for radio resource(s). TheUE 102 may then or in parallel transmit the message/element. Uponreceiving the message/element, a UE 102 may stop transmission on thesidelink on one or more resource blocks (RBs) indicated by themessage/element. The message/element may be related to one or more RBs.The mute operation indicated by the message/element may be applicablefor a finite amount of time, in some embodiments. In a non-limitingexample, the message/element may be referred to, without limitation, asa “radio resource free request message.”

In some embodiments, including but not limited to embodiments in whichthe PSCCH is used for a mute indication, an existing/legacy sidelinkcontrol information (SCI) or other SCI format may be used for one ormore of the following: to indicate a mute operation, to indicateinformation related to the mute operation, to indicate resources for themute operation, to reserve sidelink resources and/or other. In somecases, reuse of legacy SCI formats (including but not limited to SCIFormat 1A in a 3GPP LTE standard) may simplify integration of suchsignaling in legacy LTE-V2V sidelink frameworks. Alternatively, otherSCI formats and/or modification of legacy SCI formats may be used.

In some embodiments, including but not limited to embodiments in whichthe PSCCH is used for a mute indication, the SCI signaling in the PSCCHmay include priority information. For instance, transmissions with lowerpriority are to mute transmission on indicated resources and are toexclude those resources from candidate resources for selection. In someembodiments, the SCI signaling may include frequency resource locationinformation. For instance, a set of frequency sub-channels, sub-bands orphysical resource blocks (PRBs) may be indicated. In some cases, toincrease reliability and/or to avoid near-far problems at the sidelinkreceiver side, an entire set of available frequency resources (forsidelink communication) may be indicated as occupied so that FDM type oftransmission may be precluded. In some scenarios, the TTI across allcomponent carriers may be considered as reserved.

In some embodiments, the SCI signaling may include time resourcelocation information. For instance, a set of subframes or slots or timetransmission intervals (TTIs) periodically occurring in time may beincluded. In some embodiments, the SCI signaling may include a resourcereservation period, for instance a period of muted/reserved resourceoccasions. In some embodiments, the SCI signaling may include amute/reservation interval. For instance, a timer configuration toindicate for how long a command is supposed to be valid may be included.In some embodiments, the SCI signaling may include a sidelink resourcepool ID. For instance, the SCI signaling may indicate which sidelinkpool should not be used for transmission, and this may rely on dynamicactivation/deactivation of pre-configured sidelink resource poolsavailable for transmission, in some cases. In some embodiments, the SCIsignaling may include a resource allocation mode indication. In anon-limiting example, the SCI signaling may indicate whether a mutecommand is applicable to Mode-3 (eNB 104/gNB 105 controlled UEs 102) orto Mode-4 (UEs 102 using autonomous resource selection) or to both modesof operation.

In some embodiments, the SCI signaling may include location information.For instance, the location information may include absolute or relativecoordinate of UE 102, a zone ID, a radius in which UEs 102 are supposedto mute transmission and/or other information. In some embodiments, theSCI signaling may include a sidelink carrier ID. For instance, the SCIsignaling may indicate a sidelink carrier or carrier set in whichresources are supposed to be muted. In some embodiments, the SCIsignaling may include a hop counter for resource reservation/muterequest. For instance, in cases in which signaling is relayed, the UE102 may increment a relay hop counter.

In some embodiments, for mode-3 (gNB 105 controlled) operation, a mode-3UE 102 may request the gNB 105 to indicate resource reservation/mutethrough Uu air-interface. In addition, a mode-3 UE 102 may signal suchindication over PSCCH. In some embodiments, for mode-4 (UE 102autonomous) operation, a mode-4 UE 102 may signal resource reservationand mute directly in PSCCH using SCI signaling. The UE 102 may avoidreservation of resources that are already occupied by other UEs 102.

In some embodiments, for mode-3 (gNB 105 controlled) operation, a mode-3UE 102 that detects sidelink request for mute/reservation of resource(s)on sidelink may report information about such resources to eNB 104/gNB105 to prevent scheduling on such resources. The mode-3 UE 102 thatdetects sidelink request for mute/reservation of resource on sidelinkmay relay this information if predefined conditions for relaying aremet.

In some embodiments, for mode-4 (UE 102 autonomous) operation, a mode-4UE 102 that detects sidelink request for mute/reservation of resource onsidelink may relay this information, if predefined conditions forrelaying are met (for instance, if a hop counter is below threshold orRSRP value is below threshold). The mode-4 UE 102 that detects sidelinkrequest for mute/reservation of resource on sidelink may exclude thoseresources from the set of candidate resources for selection.

In some embodiments, a PSSCH indication may include a sidelink V2X MACCONTROL CE. In some embodiments, a broadcast mode may be used, althoughthe scope of embodiments is not limited in this respect. The MAC controlCE may include one or more of the following: a command type, such asmute, mute release and/or other; priority information, for instance thetransmissions with lower priority are to mute transmission on indicatedresources and are to exclude those from candidates resources forselection; frequency resource location information, such as a set offrequency sub-channels, sub-bands, PRBs and/or other; a list of IDs(such as destination-layer2-ids and/or other): time resource locationinformation, such as a set of subframes or slots periodically occurringin time: a resource reservation interval/period, such as a period ofmuted resource occasions; a mute/reservation interval, for instance atimer configuration to indicate for how long a command is to be valid(otherwise, the eNB 104/gNB 105 may periodically signal this command, insome embodiments); a sidelink resource pool ID, such as which sidelinkpool should not be used for transmission (in some cases, this may relyon dynamic activation/deactivation of pre-configured sidelink resourcepools available for transmission): location information, such as an IDof a geographical area/zone (including but not limited to a zone ID of a3GPP standard) for which the command was issued; a resource allocationmode indication, for instance whether a mute command is applicable toMode-3 (eNB 104/gNB 105 controlled UEs 102) or to Mode-4 (UEs 102 thatuse autonomous resource selection) or both modes of operation; asidelink carrier ID, for instance an indication of sidelink carrier orcarrier set where resources are to be muted; a hop counter for resourcereservation/mute request; and/or other information.

In some embodiments, for mode-3 (eNB controlled) operation, a mode-3 UE102 may request gNB 105 to indicate resource reservation/mute through Uuair-interface using the MAC CE MUTE COMMAND. In some embodiments, formode-4 (UE autonomous) operation, a mode-4 UE 102 may signal resourcereservation and mute in PSSCH using MAC CE MUTE COMMAND. The UE 102 mayavoid reservation of resources that are already occupied by other UEs102.

In some embodiments, for mode-3 (eNB controlled) operation, a mode-3 UE102 that detects a sidelink request for mute/reservation of resource onsidelink may report information about such resources to eNB 104/gNB 105to prevent scheduling on such resources. In some embodiments, for mode-3(eNB controlled) operation, a mode-3 UE 102 that detects a sidelinkrequest for mute/reservation of resource on sidelink may relay thisinformation if predefined conditions for relaying are met.

In some embodiments, for mode-4 (UE autonomous) operation, a mode-4 UE102 that detects a sidelink request for mute/reservation of resource onsidelink may relay this information if predefined conditions forrelaying are met. In some embodiments, for mode-4 (UE autonomous)operation, a mode-4 UE 102 that detects a sidelink request formute/reservation of resource on sidelink may exclude the resources fromthe set of candidate resources for selection.

In some embodiments, upon receiving a high priority emergency signal, aUE 102 may relay the signal to other UEs 102 or eNBs 104/gNBs 105. Insome embodiments, the relay functionality may be handled in the physicallayer. For instance, if the UE 102 decodes a DCI format or a SCI formatwith a specific priority and if the number of hops is less than apre-configured threshold, the UE 102 may broadcast the transport blockto other devices.

In some embodiments, the relay functionality may be handled in the MAClayer. For instance, when the MAC receives a MAC PDU with a specificpriority and the number of hop is less than a threshold, the MAC mayrequest the physical layer to broadcast this message with the samepriority.

In some embodiments, a number of hops may be indicated in the emergencymessage. Each re-transmitting device may decrement (or increment) a hopcounter. When the count reaches a threshold and/or if a latency budgetis expired, devices may refrain from further retransmission of themessage. In a non-limiting example, the threshold to limit the number ofhops may be pre-configured in the device. In another non-limitingexample, the threshold to limit the number of hops may be configured bythe eNB 104/gNB 105, for instance by usage of a parameter in a message(such as an SIB, SIB 21 and/or other).

FIG. 10 illustrates example signaling that may be exchanged inaccordance with some embodiments. FIG. 11A, FIG. 11B, and FIG. 11Cillustrate an example of a medium access control (MAC) control element(CE) that may be exchanged in accordance with some embodiments. Inreferences herein, “FIG. 11” may include FIG. 11A, FIG. 11B and FIG.11C. FIG. 12 illustrates an example of a system information block (SIB)element that may be exchanged in accordance with some embodiments. FIG.13 illustrates example signaling that may be exchanged in accordancewith some embodiments. It should be noted that the examples shown inFIGS. 10-13 may illustrate some or all of the concepts and techniquesdescribed herein in some cases, but embodiments are not limited by theexamples. For instance, embodiments are not limited by the name, number,type, size, ordering, arrangement and/or other aspects of theoperations, messages, elements, signaling, eNBs 104, UEs 102, resourcesand other elements as shown in FIGS. 10-13. Although some of theelements shown in the examples of FIGS. 10-13 may be included in a 3GPPLTE standard, 5G standard, NR standard and/or other standard,embodiments are not limited to usage of such elements that are includedin standards.

Referring to FIG. 10, examples of signaling are shown. It should benoted that vehicles 1011-1014 are shown in FIG. 10, but examples are notlimited to vehicles or to devices that are associated with vehicles. Ina non-limiting example, a UE 102 and/or device may be integrated with avehicle. In another non-limiting example, a UE 102 and/or device may bephysically located within the vehicle (such as carried by a person inthe vehicle, sitting in the seat of a vehicle and/or other). In someembodiments, a UE 102 and/or other device (which may or may not beassociated with a vehicle) may transmit and/or receive some or all ofthe signaling shown in FIG. 10.

As indicated by 1035, the eNB 1004 may transmit network signaling forone or more of the following: to request that one or more UEs 102 and/ordevices mute transmissions; reserve sidelink resources; and/or other. Asindicated by 1020, Uu uplink signaling (PUCCH, PUSCH and/or other) maybe used for one or more of the following: to request high reliabilitytransmission on a sidelink resource grid (such as 1040); and/or other.As indicated by 1025, Uu downlink signaling (PDCCH. PDSCH, PMCH and/orother) may be used for one or more of the following: to request muting,to indicate sidelink resource reservation for high reliabilitytransmission on a sidelink resource grid (such as 1040); and/or other.As indicated by 1030, PC5 sidelink signaling (PSCCH, PSSCH and/or other)may be used for one or more of the following: to request highreliability transmission on a sidelink resource grid (such as 1040);and/or other.

The sidelink resource grid 1040 may include one or moresubchannels/subbands/PRBs (1042) and one or more subframes/slots (1044).In some cases, one or more of the following may occur (which may be aresult of signaling described above, although the scope of embodimentsis not limited in this respect): muting of sidelink transmissions;exclusion of sidelink resources from candidate set of resources forselection/reselection; reservation of resources for dedicatedUEs/sidelink transmission with high reliability; and/or other.

Referring to FIG. 11, an example MAC CE 1100 is shown. Some embodimentsmay not necessarily include all the parameters shown in FIG. 11. Someembodiments may include one or more additional parameters not shown inFIG. 11. Embodiments are not limited to the names, ordering and/or otheraspects of the parameters shown in FIG. 11. Some or all of theparameters shown in FIG. 11 may be included in a 3GPP LTE standard, 5Gstandard, NR standard and/or other standard, but embodiments are notlimited to usage of parameters that are included in standards. In someembodiments, one or more alternate parameters (which may or may not beincluded in a standard) may be used instead of one or more of theparameters shown in FIG. 11.

The MAC CE 1100 may include one or more of the following: a CMD field1101 (such as a mute command that may take values such as “start”,“stop”, and/or other), the P field 1102 (which may indicate whether apriority bitmap is present), the Z field 1103 (which may indicatewhether a zone bitmap is present), one or more reserved bits 1104, apriority bitmap 1105 (which may indicate one or more priorities forwhich the command is applicable) and a Zone ID bitmap 1106 (which mayindicate one or more Zone IDs for which the command is applicable). Insome embodiments, the MAC CE 1100 may include any number (includingzero) of other parameters and/or information.

As indicated by 1105, the eNB 104 and/or gNB 105 may transmit a MAC CE(which may include the mute command) to the UE 102, in some embodiments.As indicated by 1110, a first UE 102 may transmit a MAC CE (which mayinclude the mute command) to a second UE 102, in some embodiments.

Referring to FIG. 12, an example SIB element is shown. Some embodimentsmay not necessarily include all the parameters shown in FIG. 12. Someembodiments may include one or more additional parameters not shown inFIG. 12. Embodiments are not limited to the names, ordering and/or otheraspects of the parameters shown in FIG. 12. Some or all of theparameters shown in FIG. 12 may be included in a 3GPP LTE standard, 5Gstandard, NR standard and/or other standard, but embodiments are notlimited to usage of parameters that are included in standards. In someembodiments, one or more alternate parameters (which may or may not beincluded in a standard) may be used instead of one or more of theparameters shown in FIG. 12.

The SIB element 1200 may include one or more of the following: a mutepriority list 1211, a zone ID list 1212, a mute RB subchannel parameter1213, a mute periodicity parameter 1214 and any number (including zero)of other parameters and/or information 1215. In some embodiments, theSIB element 1200 may include a “Mute config element” 1210, and one ormore of the parameters 1211-1215 may be included in the “Mute configelement” 1210. The SIB element 1200 may also include any number(including zero) of other parameters and/or information 1220.

In some embodiments, one or more resource allocation modes for V2Vcommunication may be used. For instance, mode-3 (eNB controlled)operation and/or mode-4 (UE autonomous) operation may be used. In eNBcontrolled mode (mode-3), the resource for V2V transmission may becontrolled and/or assigned by the gNB 105 based on one or more factors,including but not limited to vehicle location information reported bythe UE 102. In UE-autonomous mode (mode-4), the resource(s) fortransmission may be selected autonomously by the UE 102 based on one ormore factors, including but not limited to information determined by asensing procedure, information determined by a resource selectionprocedure and/or other information. In some embodiments, resources maybe shared between UEs for mode-3 and mode-4 transmissions. Accordingly,techniques to enable seamless coexistence between two V2V transmissionmodes (such as mode-3 and mode-4) may be used.

It should be noted that a UE 102 configured to operate in accordancewith mode-3 may be referred to as a “mode-3 UE” for clarity, but suchreferences are not limiting. For instance, an operation described hereinas performed by a mode-3 UE 102 may be performed by a UE 102 and/orother device, in some embodiments. In addition, a UE 102 configured tooperate in accordance with mode-4 may be referred to as a “mode-4 UE”for clarity, but such references are not limiting. For instance, anoperation described herein as performed by a mode-4 UE 102 may beperformed by a UE 102 and/or other device, in some embodiments.

In some embodiments, measurements and/or reporting mechanisms performedby mode-3 UEs 102 may be reported to the gNB 105 to assist in resourcescheduling decisions. The measurements and/or reporting mechanisms mayprovide information on resource utilization, a set of candidate resourcethat may be used for transmission, additional complementarv information(such as a priority of a transmission that occupies a given set ofresources) and/or other information.

In some embodiments, triggering conditions to report additionalinformation by mode-3 UEs 102 may be used, including periodic andevent-triggered reporting modes and configuration of the report content.In some embodiments, signaling of a resource reservation period by Mode3 UEs 102 transmitting in resources allocated in semi-persistent mannermay be used. In some embodiments, a mechanism to introduce restrictionon gNB 105 resource reservation duration may be used. This mechanism maybe used when the UE 102 operates in a semi-persistent resourceallocation mode, although the scope of embodiments is not limited inthis respect.

In some embodiments, a UE-autonomous resource allocation mode may beused within and outside of network coverage scenarios. The eNBcontrolled mode may be used within network coverage. In some cases, thegNB 105 controlled mode may be used within network coverage and UEautonomous mode may be used for UEs 102 that are out of coverage of thegNB 105. In some cases, both modes may be supported within networkcoverage (that is, for UEs 102 within network coverage). In anon-limiting example, at the network edge, both modes may coexist andmay share the same resource pools. In another non-limiting example, thenetwork may want to operate certain V2X services in mode-3 and mayoffload other services to mode-4. In another non-limiting example, thenetwork may provide mode-3 for services with higher priority, and mayoffload lower priority services to mode-4.

In some embodiments, for mode-3, the gNB 105 may utilize vehiclegeo-location information to provide UE resource assignment. In somecases, including but not limited to cases in which the UEs 102 thatperform V2V transmissions in the resource pool operate in mode-3, thegNB 105 may orthogonalize UE 102 transmissions based on locationinformation and/or inter-cell coordination techniques. However, thecoexistence in cases in which a mixture of mode-3 UEs 102 and mode-4 UEs102 share the same resource pool may become problematic. For instance,the gNB 105 may not necessarily be aware about actual radio-environmentand resource utilization, in some cases.

In some embodiments, mode-4 UEs 102 may perform sensing and resourceselection operations in an effort to avoid collisions and/or to selectless congested resources while respecting the priority informationindicated by other UEs 102 in SCI Format 1. The UEs 102 that reselectresources may perform one or more of the following operations: performreceive power (radio-distance) measurements for some or all candidateresources; select a candidate set of less congested resources; randomlyselect resource(s) for transmission from the candidate set of resources;and/or other operation(s).

In some cases, including but not limited to mixed mode-3 and mode-4scenarios, one or more techniques may be used in an effort to avoidscheduling of mode-3 transmissions on resources occupied by mode-4 UEs102. In some cases, there may not necessarily be exclusive partitioningof resources among mode-3 UEs 102 and mode-4 UEs 102.

In some cases, including but not limited to shared resource poolscenarios, additional mode-3 UE 102 reporting may be used in an attemptto ensure proper operation, to respect mode-4 transmissions and/or otherpurpose.

In some embodiments, in order to assist the gNB 105 in scheduling ofmode-3 transmissions and/or other purpose, the mode-3 UEs 102 maycollect and/or report information about radio-environment and resources.For instance, a mode-3 UE 102 may report one or more measurements (suchas an S-RSSI power measurement and/or other) per configured set ofresources for a time interval (such as a resource selection windowand/or other).

In some embodiments, the mode-3 UE 102 may report the set of candidateresources for selection (for instance, resources with received powerbelow certain S-RSSI or PSCCH/PSSCH-RSRP threshold). In someembodiments, the mode-3 UE 102 may use one or more techniques and/oroperations of a mode-4 sensing and/or resource selection procedure,although the scope of embodiments is not limited in this respect.

n some embodiments, some information may be configured by the gNB 105.Examples of such information include, but are not limited to, a size ofa candidate resource set, resource configuration (such as a number ofPRBs, a number of sub-bands, a size of frequency resources, a number ofsub-frames, a number of TTIs, a size of time resources and/or otherinformation that may be used for transmission, resource selection windowand/or other purpose) and/or other information.

In some embodiments, the UE 102 may report information about someresources, such as resources in which the UE 102 detects a high prioritytransmission. In this case, the UE 102 may be configured to reportresources (for instance, a set of frequency resources within a timewindow) to provide information about priority of transmission onallocated resources. In some embodiments, the UE 102 may be configuredto monitor and report certain priority levels under predefined reportingconditions (such as a level of priority and corresponding received powercontribution for a given priority level and/or other). In addition, theUE 102 may be configured to report if a resource is reserved withcertain set of resource reservation periods (for instance, 100 msec, 200msec and/or other) and to refrain from reporting for transmissions withhigher resource reservation periods.

In some embodiments, the UE 102 may report a resource selection mode(such as mode-3 or mode-4) of a transmission detected by the UE 102. Insome cases, signaling of the resource selection mode (mode-3 or mode-4)may be used by the gNB 105 for resource selection. In some embodiments,the UE 102 may report a V2X service type indicated by other UEs 102occupying certain resources. If the UE 102 detects that a significantportion of received power is transmitted by a UE 102 not controlled bythe network, the network (gNB 105 or other component) may refrain fromusage and/or assignment of this resource. In some embodiments, the gNB105 may optimize resource allocation and reuse resources which aresignaled as occupied resources. To enable this operation, an additionalfield (mode-3/mode-4 indicator) may be included in an element (such asan SCI, MAC CE, information element, RRC signaling and/or other) tosignal whether the occupied resource were selected with gNB 105assistance.

In some embodiments, UE 102 reporting may be UE specifically configuredas periodic (for instance, sent to the gNB 105 every “Treport” msec,such as Treport=1000 msec and/or other value). Embodiments are notlimited to the “Treport” parameter, as any parameter related toperiodicity may be used. In some embodiments, the UE 102 reporting maybe event-triggered based on one or more of the following events:resource reselection was triggered by eNB; a time from a previous reporthas expired; a time for a new resource (re)-selection has come: ameasured CBR level is below or above a threshold; a transmissionpriority above a preconfigured set of values is detected: one or moretransmission parameters have been changed (such as a required resourcereservation interval, an amount of required resources and/or otherparameter); and/or other event.

In some embodiments, in mode-3, sidelink transmissions may bedynamically or semi-statically scheduled by the gNB 105. In anon-limiting example, SPS activation/deactivation commands in DCI Format5A may be used. In case of dynamic scheduling, the coexistence betweenmode-3 and mode-4 transmissions may be more problematic since mode-3transmission assignments may look like random resource selections fromthe perspective of the UE 102 that performs sensing and resourceselection. Therefore, a mode-4 UE 102 may not necessarily take intoaccount mode-3 transmissions scheduled dynamically in its own resourceselection. On the other hand, when mode-3 utilizes SPS schedulingmechanism, the information about transmission period may be signaled bymode-3 UE 102 in SCI format 1, according to configured value of SPStransmission period. If the transmission period is indicated as aresource reservation interval in SCI-Format 1, the mode-4 UEs 102 maytake it into account in sensing and resource selection procedures(including but not limited to procedures of a 3GPP standard and/or otherstandard). However, this impact on mode-4 UEs 102 may be significant,for instance if scheduling decisions by the gNB 105 do not respectmode-4 UE 102 resource selection decisions.

In some embodiments, a mode-4 UE 102 may reselect resources aftertransmission of a certain number of transport blocks (TBs). In someembodiments, the mode-4 UE 102 may then reselect resource upon a TBcounter expiration condition. In case of a gNB 105 scheduled mode, amode-3 UE 102 may keep resources for a relatively long time. In somecases, this may lead to certain performance loss as the mode-4 UEs 102may be limited in terms of resource selection.

In some embodiments, mode-3 UEs 102 may reselect resources after certainamount of time (for instance, the gNB 105 may periodically reassignresources for V2V communication). The corresponding triggers to reassignresources for mode-3 transmissions may be defined in case of gNB 105controlled operation. In some embodiments, a counter based trigger maybe applicable for mode-3 operation in resource pool shared with mode-4UEs 102. Alternatively, this mechanism may be used to providepreferential access to resources and radio-propagation conditions formode-3 UEs 102.

In some embodiments, the gNB 105 may configure UE 102 mode-3/mode-4switching conditions, so that the UE 102 may switch from mode-4 tomode-3 and vice versa. In a non-limiting example, UE specific or cellspecific RRC or SIB signaling may be used to provide this information toUEs 102. The potential conditions may include, but are not limited to: aV2X service type or QoS requirement, a V2X service/transmission priority(such as PPPP); Uu link RSRP conditions (such as an RSRP value);required resource reservation period below or above a predefined value:a measured CBR value above or below a threshold; the UE 102 is withincertain geo-graphical area; a trigger of cell reselection; a handoverprocedure; and/or other.

In some embodiments, a method of sharing resources by mode-3 and mode-4sidelink V2V communication may comprise or may be based on one or moreof: sidelink measurement performed by mode-3 or mode-4 UEs 102 to assistgNB 105 scheduling decisions; signaling of V2X service type andmode-3/mode-4 indicator; reporting mechanism to signal UE 102 sidelinkmeasurements to gNB 105; signaling to configure conditions to performmeasurement or reporting by UEs 102; conditions for UE mode-3/mode-4switching and corresponding signaling; conditions for UE 102 mode-3resource reselection.

In some embodiments, measurements performed by UEs 102 to assist gNB 105scheduling decisions may comprise one or more of: sensing measurements,such as S-RSSI and PSCCH/PSSCH-RSRP measurements to characterize qualityof sidelink V2V resources over certain time interval (such as a sensingwindow or resource selection window); resource selection measurements,such as estimation of candidate subset of resources for selection, basedon configured resource definition (for instance, a number of PRBs) anddetermined according to sensing and resource selection procedure (forinstance, based on minimum average received power criteria); occupiedresource measurements, such as estimation of a set of resources occupiedby transmissions with indicated priority level from the preconfiguredset of priorities (or resources with received power above a certainthreshold, for instance congested resources); resources occupied bymode-3 or mode-4 transmissions or by given V2X service, for instanceutilizing resource reservation period from the predefined set of values;and/or other.

In some embodiments, signaling of V2X service type and mode-3/mode-4indicator may be included into the SCI format signaling (L1 signaling),MAC or RRC signaling to indicate which V2X service is delivered orwhether transmission is controlled by gNB 105 or UE-autonomous. In someembodiments, a reporting mechanism to signal UE measurements to eNB maycomprise one or more of: RRC or MAC signaling to provide UE sidelinkmeasurement report (sensing and resource selection report) to gNB 105;gNB 105 configuration signaling to configure measurements requested bygNB 105 or sidelink measurement report triggering conditions; periodicor event-triggered reporting, in which the UE reporting may be UEspecifically configured as periodic or event-triggered based on certainset of conditions. In some embodiments, signaling to configureconditions to perform measurement or reporting by UEs 102 may compriseRRC or SIB21 signaling to configure measurements reports or conditionsto perform measurements.

In some embodiments, conditions for UE mode-3/mode-4 switching andcorresponding signaling may include one or more of: condition on V2Xservice type or QoS requirement to be served by mode-3/4; condition onV2X service/transmission priority (e.g. PPPP) to be served by mode-3/4;Uu link RSRP conditions (for instance, an RSRP value); required resourcereservation period below or above predefined value to be served bymode-3/4; measured CBR value above or below certain threshold to beserved by mode-3/4; UE 102 is within certain geo-graphical area to beserved by mode-3/4; trigger of cell reselection, handover procedure;and/or other. In some embodiments, conditions for UE mode-3 resourcereselection may comprise a counter based trigger for mode-3 operation inresource pool shared with mode-4 UEs 102, restriction on amount of TBstransmitted under selected resource; and/or other.

Referring to FIG. 13, examples of signaling are shown. It should benoted that vehicles are shown for UEs 1320, 1321, 1322, 1330, and 1331are shown in FIG. 13, but examples are not limited to vehicles or todevices that are associated with vehicles. In a non-limiting example, aUE 102 and/or device may be integrated with a vehicle. In anothernon-limiting example, a UE 102 and/or device may be physically locatedwithin the vehicle (such as carried by a person in the vehicle, sittingin the seat of a vehicle and/or other). In some embodiments, a UE 102and/or other device (which may or may not be associated with a vehicle)may transmit and/or receive some or all of the signaling shown in FIG.13.

As shown in FIG. 13, the network coverage area 1307 for eNB 1305 maysupport communication with UEs 1320-1322. Accordingly, the UEs 1320-1322may perform sidelink communication in accordance with mode-3 operation,in some embodiments. The UEs 1330, 1331 may operate outside of thenetwork coverage area 1307. Accordingly, the UEs 1330, 1331 may performsidelink communication in accordance with mode-4 operation, in someembodiments.

The resource grid 1310 includes resources R1-R6, but embodiments are notlimited to this number of resources, to the number of resources in thetime dimension of grid 1310 or to the number of resources in thefrequency dimension of grid 1310. The eNB 1305 may transmit DCI 1330 tothe UE 1320 (UE0) that indicates that the UE 1320 (UE0) is to use R3.The eNB 1305 may transmit additional DCIs (such as DCI 1331 to UE 1321(UE1), DCI 1332 to the UE 1322 (UE2) and/or other DCI(s)) that mayindicate resources to be used by those UEs.

In the example shown in FIG. 13, the UE 1331 (UE4) may transmit on R1,and this may be detected by the UE 1321 (UE1) and by the UE 1322 (UE2).In addition, the UE 1330 (UE3) may transmit on R5, and this may bedetected by the UE 1322 (UE2). The UE 1321 (UE1) may transmitinformation (such as 1351) to the eNB 1305. Such information may includean indication that the UE 1321 (UE1) has detected transmission in R1and/or other information. The UE 1322 (UE2) may transmit information(such as 1352) to the eNB 1305. Such information may include anindication that the UE 1322 (UE2) has detected transmission in R1 and R5and/or other information.

Candidate resource sets (such as CRS 1341 for UE 1321 and CRS 1342 forUE 1322) may be modified based at least partly on detected transmissionsand/or messages from the eNB 1305.

In Example 1, an apparatus of a Generation Node-B (gNB) may comprisememory. The apparatus may further comprise processing circuitry. Theprocessing circuitry may be configured to allocate a resource pool ofphysical resource blocks (PRBs) and sub-frames for vehicle-to-vehicle(V2V) sidelink transmissions. The processing circuitry may be furtherconfigured to decode, from a User Equipment (UE), an uplink controlmessage that indicates that the UE requests a V2V sidelink transmissionof a prioritized message. The processing circuitry may be furtherconfigured to select, for the V2V sidelink transmission of theprioritized message, one or more PRBs of the resource pool and one ormore sub-frames of the resource pool. The processing circuitry may befurther configured to encode, for transmission to the UE and to otherUEs, a downlink control message that indicates: the selected PRBs, theselected sub-frames, and that the other UEs are to mute sidelinktransmissions in the selected PRBs in the selected sub-frames to enablethe V2V sidelink transmission of the prioritized message. The memory maybe configured to store information identifying the selected PRBs and theselected sub-frames.

In Example 2, the subject matter of Example 1, wherein the downlinkcontrol message is a first downlink control message. The processingcircuitry may be further configured to encode, for transmission, a firstdownlink control message that indicates the PRBs of the resource pooland the sub-frames of the resource pool.

In Example 3, the subject matter of one or any combination of Examples1-2, wherein the downlink control message may further indicate a timeduration for which the other UEs are to mute the sidelink transmissionsin the selected PRBs in the selected sub-frames.

In Example 4, the subject matter of one or any combination of Examples1-3, wherein the downlink control message may be a medium access control(MAC) control element (CE) included in a physical downlink sharedchannel (PDSCH).

In Example 5, the subject matter of one or any combination of Examples1-4, wherein the downlink control message may be a physical downlinkcontrol channel (PDCCH). The PDCCH may include a downlink controlinformation (DCI) that includes the selected PRBs and the selectedsub-frames.

In Example 6, the subject matter of one or any combination of Examples1-5, wherein the downlink control message may be a broadcast systeminformation block (SIB).

In Example 7, the subject matter of one or any combination of Examples1-6, wherein: the uplink control message may be included in a physicaluplink shared channel (PUSCH), or the uplink control message may be aphysical uplink control channel (PUCCH).

In Example 8, the subject matter of one or any combination of Examples1-7, wherein the uplink control message may indicate one or more of: atransmission period for the V2V sidelink transmission of the prioritizedmessage, a number of PRBs for the V2V sidelink transmission of theprioritized message, and a buffer status report. The processingcircuitry may be further configured to select the PRBs and thesub-frames for the V2V sidelink transmission of the prioritized messagebased at least partly on the uplink control message.

In Example 9, the subject matter of one or any combination of Examples1-8, wherein the gNB may be arranged to operate in accordance with aThird Generation Partnership Project (3GPP) protocol. The gNB may beconfigured for mode-3 operation, wherein the gNB is to select the PRBsand the sub-frames of the resource pool for the V2V sidelinktransmissions.

In Example 10, the subject matter of one or any combination of Examples1-9, wherein the gNB may be arranged to operate in accordance with aThird Generation Partnership Project (3GPP) protocol. The uplink controlmessage may be received over an uplink Uu interface. The downlinkcontrol message may be transmitted over a downlink Uu interface.

In Example 11, the subject matter of one or any combination of Examples1-10, wherein the downlink control message is a first downlink controlmessage, and the uplink control message is a first uplink controlmessage. The processing circuitry may be further configured to encode,for transmission, a second downlink control message that instructs theUE to sense a sidelink channel in accordance with one or more channelsense parameters. The processing circuitry may be further configured todecode, from the UE, a second uplink control message that indicates oneor more results of the sense operation in accordance with the channelsense parameters.

In Example 12, the subject matter of one or any combination of Examples1-11, wherein the downlink control message is a first downlink controlmessage. The processing circuitry may be further configured to encode,for transmission, a second downlink control message that instructs theUE to perform radio-layer measurements within sidelink resource pools todetermine candidate resources available for sidelink transmission.

In Example 13, the subject matter of one or any combination of Examples1-12, wherein the second downlink control message is a radio resourcecontrol (RRC) message. The RRC message may include one or moretriggering conditions for measurement and reporting of results by theUE.

In Example 14, the subject matter of one or any combination of Examples1-13, wherein the triggering conditions are based on one or more of: areceived power threshold or a reference signal received power (RSRP)threshold for detected sidelink transmissions, and a priority thresholdfor detected sidelink transmissions.

In Example 15, the subject matter of one or any combination of Examples1-14, wherein the RRC message may indicate that the UE is to use areporting format that indicates, from the sidelink resource pools:recommended resources for allocation for sidelink transmissions, orresources to refrain from allocation for the sidelink transmissions.

In Example 16, the subject matter of one or any combination of Examples1-15, wherein the apparatus may further include a transceiver to receivethe uplink control message and to transmit the downlink control message.

In Example 17, the subject matter of one or any combination of Examples1-16, wherein the processing circuitry may include a baseband processorto select the PRBs and the sub-frames for the V2V sidelink transmissionof the prioritized message.

In Example 18, a computer-readable storage medium may store instructionsfor execution by one or more processors to perform operations forcommunication by a Generation Node-B (gNB). The operations may configurethe one or more processors to allocate a resource pool of physicalresource blocks (PRBs) and sub-frames for: mode-3 vehicle-to-vehicle(V2V) sidelink transmissions in accordance with resource selection bythe gNB, and mode-4 V2V sidelink transmissions in accordance withautonomous resource selection by User Equipments (UEs). The operationsmay further configure the one or more processors to encode, fortransmission to a first UE, a downlink control message that indicatesone or more parameters for a channel sense measurement for the resourcepool. The operations may further configure the one or more processors todecode, from the first UE, an uplink control message that indicates thechannel sense measurement. The operations may further configure the oneor more processors to select, based at least partly on the channel sensemeasurement, one or more resources of the resource pool for a mode-3 V2Vsidelink transmission by a second UE.

In Example 19, the subject matter of Example 18, wherein the channelsense measurement may be a sidelink received signal strength indicator(S-RSSI).

In Example 20, the subject matter of one or any combination of Examples18-19, wherein the parameters for the channel sense measurement mayinclude a number of PRBs a number of sub-frames.

In Example 21, the subject matter of one or any combination of Examples18-20, wherein the downlink control message is a first downlink controlmessage. The operations may further configure the one or more processorsto encode, for transmission to the second UE, a second downlink controlmessage that indicates the selected resources for the mode-3 V2Vsidelink transmission by a second UE.

In Example 22, the subject matter of one or any combination of Examples18-21, wherein the resources selected for the mode-3 V2V sidelinktransmission by the second UE are second resources. The channel sensemeasurement may be related to first resources of the resource pool. Theoperations may further configure the one or more processors todetermine, based at least partly on the channel sense measurement,whether the first resources are unavailable for mode-3 V2V sidelinktransmissions. The operations may further configure the one or moreprocessors to, if it is determined that the first resources areunavailable for mode-3 V2V sidelink transmissions, select the secondresources from candidate resources that exclude the first resources.

In Example 23, an apparatus of a User Equipment (UE) may comprisememory. The apparatus may further comprise processing circuitry. Theprocessing circuitry may be configured to determine that a prioritizedmessage is to be transmitted to another UE over a vehicle-to-vehicle(V2V) sidelink. The processing circuitry may be further configured toselect one or more physical resource blocks (PRBs) and one or moresub-frames to be used for transmission of the prioritized message overthe V2V sidelink. The PRBs and sub-frames may be included in a resourcepool of candidate PRBs and candidate sub-frames. The processingcircuitry may be further configured to encode, for transmission to otherUEs, a sidelink control message that indicates: the selected PRBs, theselected sub-frames, and a mute command that indicates that the otherUEs are to mute sidelink transmissions in the selected PRBs in theselected sub-frames. The processing circuitry may be further configuredto encode the prioritized message for transmission in the selected PRBsin the selected sub-frames. The memory may be configured to store atleast a portion of the prioritized message.

In Example 24, the subject matter of Example 23, wherein the processingcircuitry may be further configured to determine that the prioritizedmessage is to be transmitted over the V2V sidelink based at least partlyon an indicator generated by an application layer of the UE.

In Example 25, the subject matter of one or any combination of Examples23-24, wherein the sidelink control message may be included in aphysical sidelink shared channel (PSSCH), or the sidelink controlmessage may be a physical sidelink control channel (PSCCH) that includesa sidelink control information (SCI) that includes the selected PRBs andthe selected sub-frames.

In Example 26, the subject matter of one or any combination of Examples23-25, wherein the UE may be arranged to operate in accordance with aThird Generation Partnership Project (3GPP) protocol. The UE may beconfigured for mode-4 operation, wherein the UE is to select the PRBsand the sub-frames for V2V sidelink transmissions.

In Example 27, the subject matter of one or any combination of Examples23-26, wherein the other UE is a first UE, and the prioritized messageis received from a second UE. The processing circuitry may be furtherconfigured to encode the prioritized message for relay to the first UEin the selected PRBs in the selected sub-frames.

In Example 28, an apparatus of a Generation Node-B (gNB) may comprisemeans for allocating a resource pool of physical resource blocks (PRBs)and sub-frames for: mode-3 vehicle-to-vehicle (V2V) sidelinktransmissions in accordance with resource selection by the gNB, andmode-4 V2V sidelink transmissions in accordance with autonomous resourceselection by User Equipments (UEs). The apparatus may further comprisemeans for encoding, for transmission to a first UE, a downlink controlmessage that indicates one or more parameters for a channel sensemeasurement for the resource pool. The apparatus may further comprisemeans for decoding, from the first UE, an uplink control message thatindicates the channel sense measurement. The apparatus may furthercomprise means for selecting, based at least partly on the channel sensemeasurement, one or more resources of the resource pool for a mode-3 V2Vsidelink transmission by a second UE.

In Example 29, the subject matter of Example 28, wherein the channelsense measurement may be a sidelink received signal strength indicator(S-RSSI).

In Example 30, the subject matter of one or any combination of Examples28-29, wherein the parameters for the channel sense measurement mayinclude a number of PRBs a number of sub-frames.

In Example 31, the subject matter of one or any combination of Examples28-30, wherein the downlink control message is a first downlink controlmessage. The apparatus may further comprise means for encoding, fortransmission to the second UE, a second downlink control message thatindicates the selected resources for the mode-3 V2V sidelinktransmission by a second UE.

In Example 32, the subject matter of one or any combination of Examples28-31, wherein the resources selected for the mode-3 V2V sidelinktransmission by the second UE are second resources. The channel sensemeasurement may be related to first resources of the resource pool. Theapparatus may further comprise means for determining, based at leastpartly on the channel sense measurement, whether the first resources areunavailable for mode-3 V2V sidelink transmissions. The apparatus mayfurther comprise means for, if it is determined that the first resourcesare unavailable for mode-3 V2V sidelink transmissions, selecting thesecond resources from candidate resources that exclude the firstresources.

The Abstract is provided to comply with 37 C.F.R. Section 1.72(b)requiring an abstract that will allow the reader to ascertain the natureand gist of the technical disclosure. It is submitted with theunderstanding that it will not be used to limit or interpret the scopeor meaning of the claims. The following claims are hereby incorporatedinto the detailed description, with each claim standing on its own as aseparate embodiment.

1. An apparatus of a Generation Node-B (gNB), the apparatus comprising: memory; and processing circuitry, configured to: allocate a resource pool of physical resource blocks (PRBs) and sub-frames for vehicle-to-vehicle (V2V) sidelink transmissions; decode, from a User Equipment (UE), an uplink control message that indicates that the UE requests a V2V sidelink transmission of a prioritized message; select, for the V2V sidelink transmission of the prioritized message, one or more PRBs of the resource pool and one or more sub-frames of the resource pool; and encode, for transmission to the UE and to other UEs, a downlink control message that indicates: the selected PRBs, the selected sub-frames, and that the other UEs are to mute sidelink transmissions in the selected PRBs in the selected sub-frames to enable the V2V sidelink transmission of the prioritized message, wherein the memory is configured to store information identifying the selected PRBs and the selected sub-frames.
 2. The apparatus according to claim 1, wherein: the downlink control message is a first downlink control message, the processing circuitry is further configured to: encode, for transmission, a first downlink control message that indicates the PRBs of the resource pool and the sub-frames of the resource pool.
 3. The apparatus according to claim 1, wherein the downlink control message further indicates a time duration for which the other UEs are to mute the sidelink transmissions in the selected PRBs in the selected sub-frames.
 4. The apparatus according to claim 1, wherein the downlink control message is a medium access control (MAC) control element (CE) included in a physical downlink shared channel (PDSCH).
 5. The apparatus according to claim 1, wherein: the downlink control message is a physical downlink control channel (PDCCH), and the PDCCH includes a downlink control information (DCI) that includes the selected PRBs and the selected sub-frames.
 6. The apparatus according to claim 1, wherein the downlink control message is a broadcast system information block (SIB).
 7. The apparatus according to claim 1, wherein: the uplink control message is included in a physical uplink shared channel (PUSCH), or the uplink control message is a physical uplink control channel (PUCCH).
 8. The apparatus according to claim 1, wherein: the uplink control message indicates one or more of: a transmission period for the V2V sidelink transmission of the prioritized message, a number of PRBs for the V2V sidelink transmission of the prioritized message, and a buffer status report, and the processing circuitry is further configured to select the PRBs and the sub-frames for the V2V sidelink transmission of the prioritized message based at least partly on the uplink control message.
 9. The apparatus according to claim 1, wherein: the gNB is arranged to operate in accordance with a Third Generation Partnership Project (3GPP) protocol, and the gNB is configured for mode-3 operation, wherein the gNB is to select the PRBs and the sub-frames of the resource pool for the V2V sidelink transmissions.
 10. The apparatus according to claim 1, wherein: the gNB is arranged to operate in accordance with a Third Generation Partnership Project (3GPP) protocol, the uplink control message is received over an uplink Uu interface, the downlink control message is transmitted over a downlink Uu interface.
 11. The apparatus according to claim 1, wherein: the downlink control message is a first downlink control message, the uplink control message is a first uplink control message, the processing circuitry is further configured to: encode, for transmission, a second downlink control message that instructs the UE to sense a sidelink channel in accordance with one or more channel sense parameters; and decode, from the UE, a second uplink control message that indicates one or more results of the sense operation in accordance with the channel sense parameters.
 12. The apparatus according to claim 1, wherein: the downlink control message is a first downlink control message, the processing circuitry is further configured to: encode, for transmission, a second downlink control message that instructs the UE to perform radio-layer measurements within sidelink resource pools to determine candidate resources available for sidelink transmission.
 13. The apparatus according to claim 12, wherein: the second downlink control message is a radio resource control (RRC) message, the RRC message includes one or more triggering conditions for measurement and reporting of results by the UE.
 14. The apparatus according to claim 13, wherein the triggering conditions are based on one or more of: a received power threshold or a reference signal received power (RSRP) threshold for detected sidelink transmissions, and a priority threshold for detected sidelink transmissions.
 15. The apparatus according to claim 13, wherein: the RRC message indicates that the UE is to use a reporting format that indicates, from the sidelink resource pools: recommended resources for allocation for sidelink transmissions, or resources to refrain from allocation for the sidelink transmissions.
 16. (canceled)
 17. The apparatus according to claim 1, wherein the processing circuitry includes a baseband processor to select the PRBs and the sub-frames for the V2V sidelink transmission of the prioritized message.
 18. A computer-readable storage medium that stores instructions for execution by one or more processors to perform operations for communication by a Generation Node-B (gNB), the operations to configure the one or more processors to: allocate a resource pool of physical resource blocks (PRBs) and sub-frames for: mode-3 vehicle-to-vehicle (V2V) sidelink transmissions in accordance with resource selection by the gNB, and mode-4 V2V sidelink transmissions in accordance with autonomous resource selection by User Equipments (UEs), encode, for transmission to a first UE, a downlink control message that indicates one or more parameters for a channel sense measurement for the resource pool; decode, from the first UE, an uplink control message that indicates the channel sense measurement; and select, based at least partly on the channel sense measurement, one or more resources of the resource pool for a mode-3 V2V sidelink transmission by a second UE.
 19. The computer-readable storage medium according to claim 18, wherein the channel sense measurement is a sidelink received signal strength indicator (S-RSSI). 20.-22. (canceled)
 23. An apparatus of a User Equipment (UE), the apparatus comprising: memory; and processing circuitry, configured to: determine that a prioritized message is to be transmitted to another UE over a vehicle-to-vehicle (V2V) sidelink; select one or more physical resource blocks (PRBs) and one or more sub-frames to be used for transmission of the prioritized message over the V2V sidelink, wherein the PRBs and sub-frames are included in a resource pool of candidate PRBs and candidate sub-frames; encode, for transmission to other UEs, a sidelink control message that indicates: the selected PRBs, the selected sub-frames, and a mute command that indicates that the other UEs are to mute sidelink transmissions in the selected PRBs in the selected sub-frames; and encode the prioritized message for transmission in the selected PRBs in the selected sub-frames, wherein the memory is configured to store at least a portion of the prioritized message.
 24. The apparatus according to claim 23, the processing circuitry further configured to: determine that the prioritized message is to be transmitted over the V2V sidelink based at least partly on an indicator generated by an application layer of the UE.
 25. The apparatus according to claim 23, wherein: the sidelink control message is included in a physical sidelink shared channel (PSSCH), or the sidelink control message is a physical sidelink control channel (PSCCH) that includes a sidelink control information (SCI) that includes the selected PRBs and the selected sub-frames. 26.-27. (canceled) 